Documentation
DocsUsing withHuman

Membership management

Invite people, manage member access and control who belongs to your organization.

Updated Oct 6, 2026

The Members page manages the people in your organization. It shows their teams, permissions and status, along with invitations waiting to be accepted.

Members

The member list is searchable by name, email, role, permission or team. Provisioned shows active and suspended members. All also includes people who have been removed.

The Role column shows each member's role: Owner, Admin, Reviewer or Auditor. On hosted withHuman, Custom means custom permission policies or team permissions give them access; hover over it to see each permission. To change someone's role, choose Change role from their menu. Permissions covers roles and access. Team administration covers adding people to teams.

Members page showing a member's permissions, team and Active status, with separate pending invitations
Members and pending invitations appear separately.

Invitations

An invitation is addressed to one email and sets the role the person receives when they join. Reviewer is selected by default. Only an owner can invite someone as an owner. On hosted withHuman, you can choose Custom permissions instead of a role and pick exactly what they can do; you can grant only access you already have and are allowed to manage.

withHuman emails the invitation when email delivery is configured. The app also provides a link you can share with the invitee. Invitations expire after seven days by default; each one shows its expiry date.

On hosted withHuman, active members and unexpired pending invitations count toward the seat limit. If an invitation is blocked by that limit, add seats in Billing or revoke an unused invitation.

Example: Inviting a reviewer

We'll invite [email protected] with the Reviewer role. Once they join, they can review requests assigned to them or their team.

Unsent invitation for reviewer@example.com with the Reviewer role selected
The invitation sets the person's role. This example has not been sent.

Pending invitations

Pending invitations shows who has not joined, the role or the initial permissions they will receive and when their invitation expires.

Resend sends the invitation again and renews the expiry. The previous link stops working. Without email delivery, the app shows the new link for you to send.

Revoke prevents an invitation from being accepted. It does not remove someone who has already joined; their access is managed as a member. To change a pending invitation's email or permissions, revoke it and create a new invitation.

Joining the organization

The invitation must be accepted with the email address it was sent to. The acceptance page lets an existing user join with their account, or a new user create an account. Organizations that use single sign-on direct the invitee to Continue with SSO.

If the invitee is signed in with a different email, they need to sign out first. An expired, revoked or replaced link cannot be used; ask the inviter for a current invitation.

Acceptance makes the person an active member with the invitation's permissions. Team membership is managed separately.

Member status

StatusWhat it means
ActiveThe person can access the organization according to their permissions.
SuspendedTheir access is paused. Their role and permissions are kept, but they cannot sign in or decide requests.
DeprovisionedThe person has been removed. Their sessions and personal API keys are revoked, their personal agents' instances are disabled, and their history is retained.

Reactivate restores a suspended member's access using their current role and permissions. Their personal API keys also work again if they are still valid. Use suspension for a temporary break: removed members cannot be reactivated from this page.

Remove ends access immediately, including access to requests already waiting for review. It also disables the instances of their personal agents and revokes those instances' credentials. It preserves past decisions and the audit trail. These changes affect this organization, not the person's memberships elsewhere.

Reviewers in active paths

Suspending or removing someone may affect who can review requests. If an active escalation path or team escalation policy names them individually, withHuman lists the affected rules before allowing the change.

Requests waiting for them as an agent's owner move to that request's fallback reviewers as soon as you suspend or remove them.

Update those rules to name another reviewer. Suspend anyway and Remove anyway let you proceed immediately, but the rules still name the unavailable person. A step that relied on them alone will have nobody to notify until it is updated. The override is recorded in Audit log.

Directory-managed members

A Directory badge means the member is managed through your identity provider's directory sync. Their status and directory-managed access are changed there. Manual status, role and permission changes are unavailable in withHuman.

Directory updates can suspend or remove a member even if a review rule names them. Keep review paths up to date when people leave or change responsibilities.

Access and history

The Members page loads the roster, teams and invitations together. To use it, you need access to view members and teams and manage invitations. Changing member status, changing roles and editing permission policies require additional access. Inviting someone also requires permission to grant the role or access you select.

You cannot suspend or remove yourself, or change your own role. Only an owner can change another owner's membership or role, and the organization must retain at least one active owner. Organization ownership explains these protections.

On hosted withHuman, View in audit log shows a member's recorded activity, and the Audit log also records invitations, membership changes and permission changes.

For API access, see Members and Invitations.