lokalise-enterprise-rbac

# Lokalise Enterprise RBAC ## Overview Manage fine-grained access to Lokalise translation projects using its built-in role hierarchy, language-level scoping, contributor groups, and organization-level SSO enforcement. Lokalise has four core roles — owner, admin, manager-level (via admin_rights), and contributor (translator/reviewer) — each configurable per project and per language. ## Prerequisites - Lokalise Team or Enterprise plan (contributor groups and SSO require Team+) - Owner or Admin role in the Lokalise organization - `LOKALISE_API_TOKEN` environment variable set (admin-level token) - `@lokalise/node-api` SDK or `curl` + `jq` for REST API access ## Instructions ### Step 1: Understand the Role Hierarchy Lokalise uses a flat role model per project, controlled by three boolean flags on each contributor: | Role | `is_admin` | `is_reviewer` | Can translate | Can review | Can manage keys | Can manage contributors | |------|-----------|--------------|--------------|-----------|----------------|----------------------| | **Admin** | `true` | `true` | Yes | Yes | Yes | Yes | | **Manager** | `false` | `true` | Yes | Yes | Limited (via `admin_rights`) | No | | **Reviewer** | `false` | `true` | Yes | Yes | No | No | | **Translator** | `false` | `false` | Yes | No | No | No | At the **team level**, users are either `admin` or `member`. Team admins can create projects and manage billing. Team members can only access projects they are explicitly added to. ### Step 2: Add C...