lokalise-enterprise-rbac
Configure Lokalise enterprise SSO, role-based access control, and team management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls for Lokalise. Trigger with phrases like "lokalise SSO", "lokalise RBAC", "lokalise enterprise", "lokalise roles", "lokalise permissions", "lokalise team". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lokalise-enterprise-rbac --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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` |
- Overview
- Prerequisites
- Instructions
- Step 1: Understand the Role Hierarchy
- Step 2: Add Contributors with Language Scoping
- Step 3: Manage Team-Level Users and Roles
- Step 4: Create Contributor Groups for Bulk Management
- Step 5: Configure SSO (Enterprise Plan Only)
- Step 6: Audit Permissions Regularly
- Step 7: Set Up Webhook for Access Change Notifications
- Output
- Error Handling
- Examples
- List All Contributors Across All Projects
set -euo pipefail
List all team members with their roles
curl -s -X GET "https://api.lokalise.com/api2/teams/${TEAM_ID}/users" \
Demote a user from admin to member
curl -s -X PUT "https://api.lokalise.com/api2/teams/${TEAM_ID}/users/USER_ID" \
Create a group for APAC translators
curl -s -X POST "https://api.lokalise.com/api2/teams/${TEAM_ID}/groups" \
Add a member to the group
curl -s -X PUT "https://api.lokalise.com/api2/teams/${TEAM_ID}/groups/${GROUP_ID}/members/add" \
Assign the group to specific projectsWhat does the lokalise-enterprise-rbac skill do?
Configure Lokalise enterprise SSO, role-based access control, and team management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls for Lokalise. Trigger with phrases like "lokalise SSO", "lokalise RBAC", "lokalise enterprise", "lokalise roles", "lokalise permissions", "lokalise team". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lokalise-enterprise-rbac --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.