> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/collaborate/member-management.md). # Member management Learn how to manage access to content for members of your organization You can [invite and remove members](/docs/collaborate/member-management/invite-members-to-your-organization.md) from your organization, manage members’ content access through [roles](/docs/collaborate/member-management/roles.md), and manage [teams](/docs/collaborate/member-management/teams.md) of members from the members’ page in your organization’s settings. ## Members & permissions Shows each person’s role, last seen date, and SSO status, if applicable. You’ll also see an overview of the [spaces](/docs/create-content/content-structure/space.md) they can access and, if you’re on the Pro plan, how many [teams](/docs/collaborate/member-management/teams.md) they’re part of. Click the **Teams** or **Access** listings for any member to jump to a list of all those teams and spaces. You can also click on any member to open their **individual member page**. Here, you can see more information about them, including their join date and active status. Select the **Teams** and **Spaces** tabs to see a list of the [teams](/docs/collaborate/member-management/teams.md) they’re a member of, and the spaces they have access to — as well as their access level for those specific spaces. --- # 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://gitbook.com/docs/collaborate/member-management.md?ask=&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.