> 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/roles.md). # Roles Learn about the roles within a Nested Knowledge Organization and nest. Roles match a person's permissions to their responsibility. They protect actions such as deleting a nest or reassigning ownership. Roles exist at two levels: the Organization and the nest. Your Organization role can determine the role you inherit on the Organization's nests. Learn how this works in [Permissions and inheritance](/collaborate/member-management/permissions-and-inheritance.md). Teams reuse Organization roles. See [Teams](/collaborate/member-management/teams.md). ### Organization Roles * **Owner:** If you create an Organization, you become its **Owner**. Only one person can hold this role. The **Owner** has every **Admin** capability and final authority over the Organization. Only the **Owner** can reassign ownership. * **Admin:** You can manage the Organization. This includes inviting and removing members, changing their roles, and working with teams, integrations, and templates on the **Organization Management** page. Like every member, you also inherit access to any nest the Organization can reach. * **Member:** You can use any nest the Organization can reach. You can't manage the Organization itself. ### Nest Roles * **Owner:** If you create a nest, you become its **Owner**. A collaborator can also become the **Owner** later. Only one person can hold this role. You can do everything an **Admin** can. You can also delete the nest and assign or reassign ownership. Reassigning ownership demotes the previous **Owner** to **Admin**. Only the new **Owner** can reverse it. * **Admin:** You can manage the nest from its **Settings** page. You can add individuals and Organizations, and configure the nest. You can't delete the nest or reassign ownership. * **User:** You can search, screen, tag, and extract data in the nest. You can't adjudicate, open **Settings**, or change who has access. ### How Someone Ends Up With a Role You can receive a role directly on a nest or inherit it from an Organization that owns or can access the nest. [Permissions and inheritance](/collaborate/member-management/permissions-and-inheritance.md) explains why an Organization's **Owners** and **Admins** become **Admins** on its nests. For the mechanics of granting access, see [Share](/collaborate/sharing-and-access.md). ### See Also


Invite Members to Your Organization	Add people who need access to every nest in your organization.	Invite Your Team
Manage or Remove Members	Change member roles, remove members, or withdraw pending invites.	Manage Or Remove Members
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/roles.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.