# General Translation Platform: Roles and permissions
URL: https://generaltranslation.com/en-US/docs/platform/dashboard/reference/roles-and-permissions.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: Understand the default Organization roles, permission categories, and how permissions inherit across Enterprises, Organizations, and projects. Reference for roles and permissions.

Roles control what members can see and do across your Organization and projects.

## Organization roles [#organization-roles]

When an Organization is created, four default roles are set up automatically:

| Role          | Description                                                                                                           |
| ------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Admin**     | Full access to all Organization and project settings, members, billing, and translations. Can delete the Organization. |
| **Developer** | Technical access to projects—API keys, GitHub integration, Locadex, and usage data. Cannot manage members or billing. |
| **Editor**    | Can read, edit, and review translations. No access to settings, members, or billing.                                  |
| **Member**    | Can view the Organization but has no specific permissions. Useful as a base role with additional per-user overrides.  |

## Enterprise roles [#enterprise-roles]

Enterprise accounts have an additional layer of roles for managing multiple Organizations. For details on Enterprise roles and permissions, [contact us](https://generaltranslation.com/en-US/enterprise/contact).

The **Members** page shows an Enterprise role badge when a member inherits access from the Enterprise. When that Enterprise role supersedes Organization roles, manage the member's access at the Enterprise level; Organization-level role and removal actions are unavailable.

## Permissions reference [#permissions-reference]

Permissions are grouped into categories. The table below shows which default roles have access to each permission.

### Organization permissions

| Permission               | Admin | Developer | Editor | Member |
| ------------------------ | :---: | :-------: | :----: | :----: |
| Update org settings      |   ✓   |           |        |        |
| Manage projects & plan   |   ✓   |           |        |        |
| Manage members           |   ✓   |           |        |        |
| View usage               |   ✓   |     ✓     |        |        |
| Read GitHub integration  |   ✓   |     ✓     |        |        |
| Write GitHub integration |   ✓   |     ✓     |        |        |
| Manage Locadex secrets   |   ✓   |     ✓     |        |        |
| Read Org context         |   ✓   |           |   ✓    |        |
| Write Org context        |   ✓   |           |   ✓    |        |
| Read Organization API keys  |   ✓   |           |        |        |
| Create & delete Organization API keys |   ✓   |           |        |        |
| Read webhooks            |   ✓   |     ✓     |        |        |
| Write webhooks           |   ✓   |     ✓     |        |        |

Audit Logs requires the **Manage Projects & plan** permission (`org:manage`) and an Enterprise plan. The default **Admin** role has this permission. At Enterprise scope, Audit Logs requires `enterprise:manage`. (See the [Audit Logs reference](/docs/platform/dashboard/reference/audit-logs)).

### Project permissions

| Permission               | Admin | Developer | Editor | Member |
| ------------------------ | :---: | :-------: | :----: | :----: |
| Update project settings  |   ✓   |           |        |        |
| Read project API keys    |   ✓   |     ✓     |        |        |
| Create & delete project API keys |   ✓   |     ✓     |        |        |
| Read project context     |   ✓   |           |   ✓    |        |
| Write project context    |   ✓   |           |   ✓    |        |
| Read Locadex automations and settings  |   ✓   |     ✓     |        |        |
| Write Locadex automations and settings |   ✓   |     ✓     |        |        |

Project and Organization API keys are separate permissions: the **Developer** role can create project API keys but not Organization API keys. Webhook permissions are Organization-scoped, and webhooks require a Team or Enterprise plan; see the [webhooks reference](/docs/platform/dashboard/reference/webhooks).

The Organization-level **Locadex > Automations** and **Locadex > Integrations** pages use the **Read GitHub integration** permission. Adding, editing, or deleting Organization-level Locadex secrets requires **Manage Locadex secrets**. Creating, editing, running, or deleting a project automation requires **Write Locadex automations and settings** for that project.

### Translation permissions

| Permission                    | Admin | Developer | Editor | Member |
| ----------------------------- | :---: | :-------: | :----: | :----: |
| Read translations             |   ✓   |           |   ✓    |        |
| Edit translations             |   ✓   |           |   ✓    |        |
| Review & approve translations |   ✓   |           |   ✓    |        |

### Roles & billing permissions

| Permission              | Admin | Developer | Editor | Member |
| ----------------------- | :---: | :-------: | :----: | :----: |
| View roles              |   ✓   |           |        |        |
| Create & delete roles   |   ✓   |           |        |        |
| Assign roles to members |   ✓   |           |        |        |
| View billing            |   ✓   |           |        |        |
| Update billing          |   ✓   |           |        |        |

## Permission inheritance [#permission-inheritance]

Permissions flow downward through the hierarchy:

**Enterprise → Organization → Project**

If a user has a permission at the Enterprise level, they automatically have it for all Organizations and projects within that Enterprise. Similarly, Organization-level permissions apply to all projects in that Organization.

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.