Agent skill

salesforce-enterprise-rbac

Configure Salesforce Profiles, Permission Sets, and Sharing Rules for enterprise access control. Use when implementing role-based access, configuring SSO with Salesforce, or setting up organization-wide sharing defaults. Trigger with phrases like "salesforce permissions", "salesforce RBAC", "salesforce profiles", "salesforce SSO", "salesforce sharing rules", "salesforce OWD". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-enterprise-rbac --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Version: 1.7.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEdit
Requires: Designed for Claude Code
Path: plugins/saas-packs/salesforce-pack/skills/salesforce-enterprise-rbac/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Salesforce Enterprise RBAC ## Overview Configure Salesforce's multi-layered security model: Profiles (baseline permissions), Permission Sets (additive permissions), Roles (record visibility), Organization-Wide Defaults (OWD), and Sharing Rules. ## Prerequisites - Salesforce System Administrator access - Understanding of your org's user hierarchy - For SSO: Identity Provider (Okta, Azure AD, etc.) with SAML 2.0 ## Instructions ### Step 1: Understand the Salesforce Security Model ``` ┌─────────────────────────────────────────────────────────────────┐ │ Layer 1: Organization-Wide Defaults (OWD) │ │ Most restrictive baseline — controls default record access │ │ Options: Private | Public Read Only | Public Read/Write │ ├─────────────────────────────────────────────────────────────────┤ │ Layer 2: Role Hierarchy │ │ Users above in hierarchy see records of users below │ ├─────────────────────────────────────────────────────────────────┤ │ Layer 3: Sharing Rules │ │ Grant access to groups of users based on criteria or ownership │ ├─────────────────────────────────────────────────────────────────┤ │ Layer 4: Manual Sharing │ │ Record owner shares individual records │ ├────────────────────

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: Understand the Salesforce Security Model
  5. Step 2: Configure Profiles for Integration Users
  6. Step 3: Permission Sets (Additive Permissions)
  7. Step 4: Organization-Wide Defaults (OWD)
  8. Step 5: SSO Integration
  9. Step 6: Verify Access Programmatically
  10. Output
  11. Error Handling
  12. Resources
  13. Next Steps
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the salesforce-enterprise-rbac skill do?

Configure Salesforce Profiles, Permission Sets, and Sharing Rules for enterprise access control. Use when implementing role-based access, configuring SSO with Salesforce, or setting up organization-wide sharing defaults. Trigger with phrases like "salesforce permissions", "salesforce RBAC", "salesforce profiles", "salesforce SSO", "salesforce sharing rules", "salesforce OWD". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-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.

Keep going