Agent skill · product strategy · jeremylongshore
salesforce-enterprise-rbac
Review and govern Salesforce enterprise access across profiles, permission sets and groups, sharing, field access, OAuth apps, SSO, and privileged roles. Use when designing access. Trigger with "review Salesforce access".
Why this skill is useful
Provides specific commands and configurations for Salesforce RBAC that the AI wouldn't reliably generate on its own.
What it needs
Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Enterprise Access and Sharing Governance Overview Build least privilege from job and workload needs through app authorization, org permissions, object and field access, record sharing, and periodic review. Prerequisites Personas and integration workloads, business functions, data classes, orgs, environments, and owners Current profiles, permission sets and groups, licenses, roles, sharing defaults and rules, field access, queues, and app policies Identity lifecycle, SSO and MFA, privileged access, break-glass, segregation, recertification, and audit requirements Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce authorization is layered: identity and app policy, license and profile baseline, permission sets or groups, object CRUD, field access, record sharing, and contextual controls. Effective access must be measured in the target org and user context. Authentication Separate human, integration, deployment, monitoring, support, and break-glass principals. Bind each to approved SSO or OAuth policy, minimum scope, lifecycle, rotation or recertification, revocation, and audit evidence. Instructions 1. Define personas and workloads with allowed actions, data, records, environments, hours, and business owners. 2. Inventory effective licenses, profiles, permissions, permission-set groups, roles, sharing defaults and rules, field access, and client apps. 3. Build an entitlement matrix from business need to effective access and identify inherited, overlapping, elevated, dormant, and conflicting grants. 4. Design the minimum profile baseline plus permission sets or groups and record-sharing model; keep integration access separate from users. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-enterprise-rbac