> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/collaborate/member-management.md). # Member Management Manage the members and their access levels within your organization. Member management controls who belongs to your Organization and what they can do. Organization members inherit access to every nest the Organization can reach. This lets you grant access once, rather than adding people nest by nest. To share one nest, use [Sharing and Access](/collaborate/sharing-and-access.md). Organization management is available to an Organization's Owner and Admins. For Organization setup, billing, activity reports, and templates, see [Organization Management](/account-management/organization-management.md). ### Manage Membership


Invite Your Team	Add people to your Organization and assign their role.	Invite Your Team
Manage or Remove Members	Change member roles, remove members, or withdraw pending invites.	Manage Or Remove Members
Roles	Understand organization and nest role permissions.	Roles
Permissions and Inheritance	Understand how organization access applies to nests.	Permissions and Inheritance
Teams	Organize members and nests into focused teams.	Teams

--- # 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.nested-knowledge.com/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.