Agent skill · marketing growth · jeremylongshore
lokalise-enterprise-rbac
Configure Lokalise enterprise SSO, role-based access control, and team
Why this skill is useful
Provides specific API commands and role management patterns for configuring Lokalise's enterprise RBAC that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires lokalise account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 adminrights), 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 LOKALISEAPITOKEN 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 isadmin isreviewer Can translate Can review Can manage keys Can manage contributors ------ ----------- -------------- -------------- ----------- ---------------- ---------------------- Admin true true Yes Yes Yes Yes Manager false true Yes Yes Limited (via adminrights) 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 Contributors with Language Scoping Step 3: Manage Team-Level Users and Roles Step 4: Create Contributor Groups for Bulk Management Groups let you assign the same permissions to multiple people at once. When you add a user to a group, they inherit the group's language scope and role across all projects the group is assigned to. Step 5: Configure SSO (Enterprise Plan Only) SSO is configured in the Lokalise dashboard, not via API. Map your IdP groups to Lokalise roles: 1. Navigate to Organization Settings > Single Sign-On 2. Select SAML 2.0 and enter your IdP metadata URL 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-enterprise-rbac