Here’s a snippet of my naming convention for profiles and permission sets.
Profiles
Profile names should start with the organization’s shortname or acronym, then a word that represents the type of user. This allows for quick search to identify which profiles are custom and used by the organization.
If the organization is “Dryad Consulting”, Examples:
- Dryad Base User
- Dryad Super User
- Dryad System Administrator
Permission Sets
The name should start with a verb, then the object name or target entity, then the details.
Title capitalization should be used, which means the first letter of each new word is capitalized. The name should end as a plural.
Commonly used verbs: Create, Read, Update, Delete, Manage.
Examples
- Manage Contacts
- Manage Accounts
- Create Allocations
- Merge Records
- Reconcile Financials
Permission Set Groups
The name should represent roles or titles within the organization.
Examples
- Donation Manager (Includes all the permission sets a donation worker would need)
- Case Manager (Includes all the permission sets a case worker would need)
The takeaway
A proper naming convention helps identify custom entities and their function. You don’t need to use this notation, but be sure to at least have one.