Agent skill · forcedotcom
service-omni-permission-set-assign
Assign the required Omni permission sets to provisioned agent users. TRIGGER when users ask to assign Omni permissions to agents, grant Omni-Channel access, add Omni_Agent permissions, repair missing Omni permission assignments, or prepare agents to use the Omni widget. DO NOT TRIGGER for arbitrary permission-set authoring, agent creation, or queue membership.
What it needs
About 3k tokens when loaded.
What this skill does
service-omni-permission-set-assign Assign one or more PermissionSets to N agent users via PermissionSetAssignment Data API POSTs. The default target is OmniAgent, the permission set granting the OmniChannel widget, presence-status access, and demo-queue visibility — without an assignment row, agents cannot open the widget or receive routed work. Detection is SOQL-based, so the skill only creates the assignments that are missing. Agent users come from service-omni-agent-users-create, and it runs alongside service-omni-presence-status-deploy so assigned agents can both open the widget and select a status. Inputs org-alias (required). count (optional, default 3, range 1..10) — must match the agent user count. permission-set-names-csv (optional, default OmniAgent) — comma-separated for multiple. Every user gets every listed set (cross-product): count=3 × 2 sets = up to 6 assignments. Preconditions and safety Target org authenticated via sf CLI, Service Cloud license, sf CLI ≥ 2.139.6. The agent users exist (service-omni-agent-users-create); a count mismatch blocks with a pointer back to that skill. The executing user has PermissionsAssignPermissionSets (standard on System Administrator) — required even for org admins; ModifyAllData alone is insufficient. At least one Omni presence status exists before OmniAgent self-heals — the bundled set grants agent capability via servicePresenceStatusAccesses for whichever curated statuses exist (e.g. AvailableCase/AvailableVoice + Busy), generated at deploy time. Run service-omni-presence-status-deploy first; the coordinator sequences presence before permset for this reason. The three-way safetowrite guard applies — assigning permission sets on a production org can escalate a real user's privileges, so it blocks with no override. Self-heal (run mode only). When the default OmniAgent set is absent, the skill deploys the bundled OmniAgent metadata once, then assigns. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/service-omni-permission-set-assign--ad92f7