Roles and permissions

Give people and services the authority their work needs, and understand how roles, resource grants, and entitlements combine.

A colleague who reads a localization engine's configuration may not need to change it, translate with it, or approve its output. Permissions separate those responsibilities. Effective access combines membership, role permissions, resource grants, feature entitlements, and the checks of the actual operation.

Roles and grants add authority. Giving someone access to one localization engine does not restrict a role that already grants access to all of them. Start with the required responsibility, then inspect every source of permission that contributes to it.

Permission catalog #

AreaPermissions
Organization administrationorg:manage_team, org:manage_billing, org:manage_settings, org:manage_api_keys, org:manage_integrations, org:delete, org:view_audit_logs
Decision poolsorg:manage_decision_pools
Localization engines and reviewengine:read, engine:translate, engine:create, engine:edit, engine:delete, engine:review_translations, org:manage_reviews
Glossariesorg:glossary:read, org:glossary:edit
Brand voicesorg:brandvoice:read, org:brandvoice:edit
Rulesetsorg:ruleset:read, org:ruleset:edit
Suggestionsorg:suggestion:read, org:suggestion:edit

Read and decide suggestions #

To read suggestions through a role, give it org:suggestion:read and read access to the relevant localization engines. To apply or dismiss suggestions, give it org:suggestion:edit and edit access to those engines. Engine permissions alone do not include suggestion permissions.

An organization member with an explicit grant to an engine can also read and decide that engine's suggestions without the role's suggestion permissions. This grant applies to that engine; it does not grant access to every engine in the organization. Membership remains required.

Review translations #

Deciding a human review requires a user identity, organization membership, and Review translations (engine:review_translations) for the engine. A signed-in user or personal API key can supply that identity. Reading review history does not grant decision authority.

Plan eligibility is checked when new review work starts. Authorized reviewers can still read and decide existing document reviews after a plan downgrade. See Feature access when diagnosing a blocked review.

Granting review authority does not make every translation wait for a person or preserve reviewed wording against later stages; those are review-policy choices.

Creating, editing, or archiving decision pools requires Manage decision pools (org:manage_decision_pools). Membership in an internal pool controls review notifications; it does not grant Review translations. See Plans and permissions for the complete requirements.

Create and maintain custom roles #

Owner is the platform-managed system role and cannot be edited or deleted. Custom roles belong to the organization. Managing them requires RBAC entitlement and org:manage_team; the caller cannot create or grant authority beyond their own effective permissions.

In Settings → Roles, select New role, enter a name and description, choose its permissions, and select Create role. Then open Settings → Team and choose the role in the member's role picker under Members. Check the saved assignment before asking the member to use it.

Only an Owner can grant or remove Owner authority, and the last Owner cannot be demoted or removed. Promote and verify a successor before an ownership change that would otherwise leave no one responsible.

Before editing a custom role, inspect the members and service keys using it. Their access can change without replacing a credential. Before deletion, reassign or revoke service keys referencing the role; those references block deletion.

Deleting a member's custom role clears the role reference without assigning another named role. That member can still have resource grants. A blank role is therefore not proof of no access.

Resource grants #

Resource grants extend a member's authority to selected localization engines, glossaries, brand voices, or rulesets. Membership is still required: a stored grant does not turn a nonmember into an organization member. Reading a localization engine can expose attached content needed to understand its configuration.

For selected access, combine a narrow role with the necessary resource grants. If the role already covers every localization engine, adding one specific grant does not narrow it. Remove the broader role authority when restriction is the goal.

Fine-grained grants can require API or MCP operations instead of a dashboard control. Human member grants and service-key scope are separate and must be checked independently.

Personal and organization service keys are available on every plan. Without RBAC, a service key can read and translate with every localization engine in its organization, but cannot edit, delete, review, or administer it. Custom roles and resource restrictions require Enterprise RBAC.

Access changes #

An RBAC entitlement transition in either direction resets members and pending invitations to Owner. That can broaden access beyond the roles previously selected. Coordinate the billing change, inspect all members and pending invitations afterward, and restore deliberate roles where applicable.

For a departure, review membership and credentials separately. Organization service keys are independent of one member's continued participation. Keep another Owner and replace caller dependencies before removing access that ongoing work needs.

Feature access helps distinguish entitlement from permission failures. Audit logs can show recorded changes, but the current role, grants, and operation determine what is allowed now.