> 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/technical-reference/identity-access-and-administration/invitations-membership-and-access-removal.md).

# Invitations, Membership, and Access Removal

Invitations add people to an organization or shared resource. Membership and role determine the access available after an invitation is accepted.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FkrsyDJJucyZ8kCxUzFl5%2FG002.mp4?alt=media&token=66311517-4b6d-498a-86ea-a80b3cd0ad84>" %}

## Before you begin

Permission to invite or manage members.

## Key concepts

| Term          | Definition                                                                                                                                            |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Invitation    | A request for an account to join an organization or shared resource. The recipient normally must accept with the intended account.                    |
| Membership    | The account’s association with an organization and assigned access. An invitation alone is not proof of accepted membership.                          |
| Role          | A set of permissions assigned to a member or supported account. Inspect the permission matrix rather than inferring access from the role name.        |
| User identity | The authenticated person or application acting on a resource. It determines access; a display name or conversation ID does not authenticate a caller. |
| Revocation    | Withdrawal of a credential or access grant. Check dependent applications and separately issued links when access changes.                             |

## Invite or remove a member

1. Invite the intended account with the appropriate role.
2. Have the recipient accept through the supported sign-in flow.

![Accept the invitation using the account that received it.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/AF6BQi4VjX2tPxolvyKl/assets/g002-g002-02-join-organization.png)

Accept the invitation using the account that received it.

3. Review membership and resource access after acceptance or removal.

The recipient has the intended membership and access.

## Behavior and limitations

An invitation is not accepted membership. Removing a member does not necessarily delete projects, provider records, or previously exported data. Review shared connections and API credentials when changing responsibilities. Check the invited email and sign-in account when acceptance does not expose the expected resources.

## Related resources

[Invitations and joining an organization](https://docs.stackai.com/guides-and-quickstarts/workspace-and-discovery/invitations-and-joining-an-organization.md)

[Organization Roles and Permissions](https://docs.stackai.com/technical-reference/identity-access-and-administration/organization-roles-and-permissions.md)


---

# 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/technical-reference/identity-access-and-administration/invitations-membership-and-access-removal.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.
