> ## Documentation Index
> Fetch the complete documentation index at: https://product-guide-starter-replace-template-content.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles and permissions

> Control who can edit content, manage settings, and administer your Mintlify project.

Mintlify projects use two built-in roles. All access is scoped to a single project — roles from one project don't carry over to others.

## Built-in roles

<CardGroup cols={2}>
  <Card title="Admin" icon="shield">
    Full access to project settings, billing, deployments, and member management. Can use the web editor and the dashboard.
  </Card>

  <Card title="Editor" icon="pen-line">
    Can create, edit, and publish pages using the web editor. Cannot access project settings, billing, or deployment configuration.
  </Card>
</CardGroup>

## What each role can do

| Action                          | Admin | Editor |
| ------------------------------- | ----- | ------ |
| Edit and publish pages          | ✓     | ✓      |
| Manage navigation and docs.json | ✓     | —      |
| Invite or remove members        | ✓     | —      |
| Configure custom domain         | ✓     | —      |
| Manage billing and plan         | ✓     | —      |
| View deployment history         | ✓     | —      |

## Git-based access

Roles in the Mintlify dashboard are separate from GitHub (or GitLab) repository permissions. Anyone with write access to your repository can push changes that trigger a deployment, regardless of their Mintlify role.

For organizations that want to restrict who can deploy, use GitHub branch protection rules to require pull request reviews before changes merge to your default branch.

## Organization-level access

If your Mintlify organization has multiple projects, admins can be granted access at the organization level to manage settings and members across all projects from a single place. Project-level roles still control what each person can do within a specific project.