> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/administration-control-plane/user-management-and-roles.md).
# User management and roles
Invite users, track membership, and enforce role-based access control.
Use this page to invite users, track invitations, and assign roles.
### Invite users
To invite users to your organization, click **Invite User**.
Enter one or more email addresses in the dialog.
Separate multiple email addresses with commas.
Then assign a role and send the invitation.
Each invited user receives an email invitation.
They can accept it by signing in or creating an account.
```
user1@company.com, user2@company.com, user3@company.com
```
### Invitation status
#### Pending
The invitation has been sent and is waiting for acceptance.
#### Accepted
The user has joined successfully.
#### Expired
The invitation is no longer valid.
Send a new invitation to restore access.
### Roles
#### Organization admin (`Org.Admin`)
Full organization-level admin access.
Organization admin can:
* manage organizations, applications, and projects
* invite users and assign permissions
* manage integrations and infrastructure
* manage billing and usage
* generate API keys
#### Organization user (`Org.User`)
Standard contributor access.
Organization user can:
* create resources
* modify owned resources
* run testing workflows
* access assigned infrastructure
Organization user cannot manage organization settings, invitations, integrations, or billing.
#### Organization member (`Org.Member`)
Read-only stakeholder access.
Organization member can:
* view assigned resources
* access reports
* participate in reviews
Organization member cannot create resources, modify resources, or manage access.
---
# 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.mozark.ai/administration-control-plane/user-management-and-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.
