> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/organization-administration/members-and-invitations.md).

# Members and invitations

Manage members to give people access to your organization. Invite new members with the appropriate role, and update roles when their responsibilities change.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FThL5ewdK9oEYkCZQzy3r%2FG088.mp4?alt=media&token=7c3bb1c4-c443-4215-9313-d3012fc3e711>" %}

## Before you start

Decide the required [role](https://docs.stackai.com/guides-and-quickstarts/organization-administration/roles-and-permissions.md) before inviting a person, and confirm whether membership is managed locally or through [SCIM](https://docs.stackai.com/guides-and-quickstarts/organization-administration/scim-provisioning.md). Use the identity provider for directory-managed lifecycle changes. The removal procedures below cover offboarding as well as onboarding.

You need permission to manage members and an available seat for a new member.

## Invite a member

Open Settings → Members and review current membership and seat availability.

![Members and seat availability](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/IFJ3FwlPqg6zLdqYGPfp/assets/g088-g088-01-members.png)

Check existing members before inviting someone who may already have access.

Enter the intended email address and choose the required Role.

![Invitation email and role](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/0aOGBh0pFJ7qUKlJsDOd/assets/g088-g088-02-invite.png)

Review both fields before selecting Invite Member.

Open Invitations to track the invitation's status.

![Invitation status and row menu](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/p3n2t38SgeuOqk34g1iT/assets/g088-g088-03-pending.png)

Use the row menu to resend or revoke only the intended invitation.

Have the recipient open the invitation with their own account and select Accept Invitation.

![Recipient invitation acceptance](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/h4KhDlVtb9ERgMrzYo77/assets/g088-g088-04-accept.png)

They should confirm the organization shown after acceptance.

## Change a member’s role

To change access, open the member's row menu and select Change Role.

![Member Change Role menu](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/qZKl3F2u4LC1rCeqPwRS/assets/g088-g088-05-role.png)

Review the permissions of the new role before saving.

Have the member inspect the features and projects available to their account.

![Member account access after a role change](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/TxNK7E8QrWYEJYpjlHmi/assets/g088-g088-06-access.png)

Check actual access and controls rather than inferring permissions from one navigation item.

Return to Members and confirm the saved role.

![Saved member role](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/lP7VSTpY2cRcdF52OCMs/assets/g088-g088-07-verify.png)

Keep the membership aligned with the person's continuing responsibilities.

## Remove a departing member

First check whether the member is locally managed or directory-managed. Coordinate ownership of ongoing work and identify application credentials the person used before removing access. Removing organization membership is not the same as revoking an API key; review [API key management](https://docs.stackai.com/guides-and-quickstarts/organization-administration/api-key-management.md) separately.

For a locally managed member:

1. Open **Settings → Members**, find the exact email address, and open the row menu.
2. Select **Remove**. In **Delete Member**, confirm the person and organization before confirming the removal. If this is the only administrator, assign another administrator first.
3. Refresh Members and verify the person is absent. Their membership in this organization and its groups is removed; their StackAI account and access to other organizations are not deleted.
4. Verify the organization's restricted resources can no longer be accessed by that person through your approved access-check process. Publicly accessible interfaces are a separate access policy.

For a SCIM-managed member, ask the identity administrator to remove the application's assignment or send the intended deactivation through the identity provider. StackAI protects directory-managed memberships from local removal. SCIM deactivation makes the organization's membership inactive; it does not delete the person's entire account. Confirm the provider operation and the resulting inactive membership in StackAI using [SCIM provisioning](https://docs.stackai.com/guides-and-quickstarts/organization-administration/scim-provisioning.md).

If the organization uses SSO without SCIM, also have IT remove the identity-provider application assignment. Removing the StackAI membership alone can allow it to be created again on the person's next authorized SSO sign-in.

If removal is blocked, record the member's email, management source, organization, and error for the organization administrator or [Support and deployment diagnostics](https://docs.stackai.com/guides-and-quickstarts/personal-settings-and-support/support-and-deployment-diagnostics.md). Do not disable SCIM to remove one person.

## Important behavior

An invitation must be accepted before the person joins. The assigned role determines their organization permissions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/organization-administration/members-and-invitations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
