lsc-user-management
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Guides Life Sciences Cloud (LSC) User Management — permission sets, permission set licenses, profiles, role hierarchy, license capacity, and territory-user associations. Use when user asks about user provisioning, permission set assignments, PSL capacity, role hierarchy, user access, license management, or why a user can't see data or features.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roz-uiSkill
- lsc-account-managementSkill
- lsc-activity-planSkill
- lsc-agentforceSkill
- lsc-app-alertsSkill
- lsc-briefingsSkill
- lsc-calendar-tot-routineSkill
- lsc-config-migrationSkill
- lsc-consent-managementSkill
- lsc-custom-scriptsSkill
- lsc-data-migrationSkill
- lsc-data-modelSkill
- lsc-db-schemaSkill
- lsc-demo-data-loadingSkill
- lsc-events-managementSkill
- lsc-field-emailSkill
- lsc-health-checkSkill
- lsc-home-page-configurationSkill
- lsc-implementation-reviewSkill
- lsc-implementationSkill
- lsc-integration-patternsSkill
- lsc-intelligent-contentSkill
- lsc-key-account-managementSkill
- lsc-lists-filtersSkill
- lsc-mobile-app-settingsSkill
- lsc-mobile-validationSkill
- lsc-next-bestSkill
- lsc-performance-validationSkill
- lsc-product-managementSkill
- lsc-provider-engagement-complianceSkill
- lsc-quick-actions-configurationSkill
- lsc-reporting-analyticsSkill
- lsc-sample-managementSkill
- lsc-surveysSkill
- lsc-territory-alignmentSkill
- lsc-troubleshootSkill
- lsc-visit-managementSkill
- salesforce-querySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Always call MCP tools to get sourced documentation: Do not answer from general knowledge alone.
- Distinctive: line 27
When the user asks about configuring or managing users, permissions, licenses, or roles, ask them which mode they prefer:
- Distinctive: line 32
Default to guided setup when connected to an org, or documentation mode if no org is connected.
- Distinctive: line 47
No territory -> guide user to Setup (requires UI or Metadata API)
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
How to Answer User Management Questions
Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.
| User asks about... | Call this tool |
| User management concepts, provisioning, best practices | get_lsc_module_docs({ module: "user-management" }) |
| Specific topic (PSLs, role hierarchy, licensing, etc.) | search_lsc_knowledge({ query: "<topic>" }) |
| Current org user configuration | check_user_config() |
| List active users (with optional filters) | list_users() or list_users({ filterBy: "profile", filterValue: "Life Science" }) |
| Permission sets and PSL capacity | list_permission_sets() |
| Assign a permission set | assign_permission_set({ permissionSetName: "...", usernames: ["..."] }) |
| Remove a permission set | unassign_permission_set({ permissionSetName: "...", usernames: ["..."] }) |
| Users without territories | list_users({ filterBy: "no-territory" }) |
| Users without PSLs | list_users({ filterBy: "no-psl" }) |
| User-territory associations | run_soql({ query: "SELECT UserId, User.Name, Territory2Id, Territory2.Name FROM UserTerritory2Association ..." }) |
Configuration Mode
When the user asks about configuring or managing users, permissions, licenses, or roles, ask them which mode they prefer:
- Show me the documentation — call
get_lsc_module_docs({ module: "user-management" })and present the relevant sections - Walk me through it — check my org and help me fix issues step-by-step (guided setup below)
Default to guided setup when connected to an org, or documentation mode if no org is connected.
Guided Setup Workflow
Step 1: Check Current State
check_user_config()Step 2: Report Findings
Present a summary of package license capacity, PSL capacity, active users by profile, permission set coverage, role hierarchy, territory-user associations, and users missing territories or PSLs.
Step 3: Propose Changes
For each issue found, propose the fix and wait for user confirmation:
- Missing PSL or permission set -> assign via tool
- No territory -> guide user to Setup (requires UI or Metadata API)
- PSL capacity low -> identify inactive users still consuming PSLs
Step 4: Apply Changes (with user confirmation)
assign_permission_set({ permissionSetName: "...", usernames: ["..."] })
unassign_permission_set({ permissionSetName: "...", usernames: ["..."] })For PSL assignments and territory associations, guide the user to Setup (these require UI or Metadata API operations).
Step 5: Verify
Re-run check_user_config() to confirm everything is configured correctly.
Tool Usage Rules
Correct Object Names
| Correct | Wrong (NEVER use) |
User | User__c |
Profile | UserProfile__c |
UserRole | RoleHierarchy__c |
PermissionSet | — |
PermissionSetAssignment | PermissionSetAssignment__c |
PermissionSetLicense | PermissionSetLicense__c |
PermissionSetLicenseAssign | PSLAssignment__c, LicenseAssignment__c |
UserTerritory2Association | UserTerritory__c, TerritoryUser__c |
PackageLicense | — |
Tool Restrictions
- DO NOT suggest OmniStudio/FlexCard/OmniScript for mobile — NOT available on LSC Mobile iPad app
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

