Org Permission Set Assign
OfficialFreeEasily assign permission sets to users in your org.
Free · Opens the source repo
What Org Permission Set Assign does
The Org Permission Set Assign skill streamlines the process of assigning permission sets to users within a Salesforce org. By leveraging the sf org assign permset command, this skill allows users to assign one or multiple permission sets to the default admin or specific users efficiently. The skill is particularly useful for administrators who need to manage user permissions quickly and effectively, especially in environments with multiple users or complex permission requirements.
When a user prompts to assign permission sets, the skill intelligently infers the necessary parameters, including the permission set names, target org, and target users. It supports batch assignments, allowing multiple permission sets to be assigned in a single command, which enhances productivity and reduces the time spent on repetitive tasks. The skill ensures that all assignments are executed with structured JSON output, making it easier to parse and handle any errors that may arise during the process.
This skill is designed specifically for Salesforce administrators and developers who need to manage user permissions without delving into the Salesforce UI. By automating the assignment process, users can focus on more critical tasks while ensuring that permissions are correctly assigned according to organizational needs. The skill's constraints and guidelines help prevent common pitfalls, such as typos in permission set names or issues with user aliases, providing a reliable tool for permission management.
When to use it
Use this skill when you need to assign permission sets to users, whether it's a single user or multiple users at once.
When not to use it
This skill is not suitable for creating permission sets or for listing existing permission sets; use other tools for those tasks.
What you can build with it
Assigning to Default Admin
Quickly assign a permission set to the default admin user without specifying any additional parameters.
Batch Assignments
Assign multiple permission sets to several users in one command, improving efficiency in user management.
Targeting Specific Users
Assign permission sets to specific users by leveraging the `--on-behalf-of` flag, ensuring tailored access.
How to install Org Permission Set Assign
View source1. Install with the skills CLI
npx skills add forcedotcom/sf-skills/dx-org-permission-set-assign --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by forcedotcomdx-org-permission-set-assign
Assigns one or more permission sets to org users using sf org assign permset. Handles all variants: default admin user, specific org targets, multiple permission sets, and assignment to specific users.
Tool Restrictions
Use ONLY the Bash tool to execute sf org assign permset. Do NOT use MCP tools like assign_permission_set — ignore them completely.
Scope
- In scope: Assigning permission sets to users via
sf org assign permset - Out of scope: Creating permission sets (use
platform-permission-set-generate), listing permission sets, checking user permissions
Required Inputs
Infer from the user's request:
- Permission set name(s): Extract from user message (can be multiple)
- Target org: Use default unless specific alias/username mentioned
- Target user(s): Default is org's default admin user; use
--on-behalf-ofif specific users mentioned
Workflow
- Match user request to command in table below
- Execute via Bash tool:
sf org assign permsetwith appropriate flags and--jsonflag - Return result
If error occurs, check the failures array in JSON output for details.
Command Decision Table
| User intent | Execute via Bash tool |
|---|---|
| Assign one permission set to default admin | sf org assign permset --name <PermSetName> --json |
| Assign multiple permission sets to default admin | sf org assign permset --name <PermSet1> --name <PermSet2> --json |
| Assign to specific org | sf org assign permset --name <PermSetName> --target-org <alias> --json |
| Assign to specific user(s) | sf org assign permset --name <PermSetName> --on-behalf-of <username1> --on-behalf-of <username2> --json |
| Assign multiple sets to specific users | sf org assign permset --name <PermSet1> --name <PermSet2> --on-behalf-of <username1> --on-behalf-of <username2> --json |
Rules / Constraints
| Constraint | Rationale |
|---|---|
Always use --json flag | Provides structured output for reliable parsing and error handling |
| Permission set names are case-sensitive | Use exact API names as they appear in the org |
Multiple --name flags can be combined in one command | More efficient than separate commands per permission set |
Multiple --on-behalf-of flags assign to multiple users | Batch assignment in single command; processed sequentially to avoid auth file collisions |
| Use CLI username aliases, not Salesforce User.Alias field | The --target-org and --on-behalf-of flags expect CLI aliases set via sf alias set, not the User object's Alias field |
| Duplicate assignments are idempotent | Re-assigning an already-assigned permission set succeeds silently |
| Partial success is possible | Command can return both successes and failures in one run; non-zero exit code if any failures |
Gotchas
| Issue | Resolution |
|---|---|
| Permission set name with spaces | Enclose in double quotes: --name "Permission Set Name" |
| "PermissionSet not found" error | Verify permission set exists in target org; check for typos in name |
| Assignment succeeds but user doesn't see permissions | Check <hasActivationRequired> in permission set metadata — may need manual activation in Setup |
| "User not found" error | Username/alias doesn't exist in target org — verify with sf org display user --target-org <alias> |
| Partial success (some users succeed, others fail) | Check JSON output — command returns both successes and failures arrays; exit code will be non-zero if any failures occurred |
Output Expectations
The command returns JSON output with status code and result details.
See examples/success_output.json and examples/error_output.json for response structures.
Reference File Index
| File | When to read |
|---|---|
examples/success_output.json | To understand successful assignment response structure |
examples/error_output.json | To handle common error scenarios |
references/cli_flags.md | For detailed explanation of all available flags |
Frequently asked questions about Org Permission Set Assign
Similar skills
Turborepo
Optimized build system for JavaScript/TypeScript monorepos.
Azure Pipelines Validation
Streamline your Azure DevOps pipeline changes locally.
Azure Developer CLI
Streamline your Azure project workflows with best practices.
Azure Container Registry CLI
Manage Azure Container Registry resources with ease.
Aspire
Build and orchestrate polyglot distributed applications seamlessly.
Vercel CLI
Manage and deploy Vercel projects from the command line.