Permissions are enabled by configuring a permission set and assigning it. This walkthrough adds a single permission to users by layering a permission set on top of their existing profile, which is the access pattern Salesforce recommends.
- Create the permission set
In Setup, go to Permission Sets and click New. Give it a clear, task-based label such as Case Delete Access. Leave the License field set to None unless the permission requires a specific user license.
- Enable the permission
Open the new permission set and choose the right section. Use Object Settings for object and field access, or System Permissions for user permissions like API Enabled. Switch on only the specific permission you intend to grant and save.
- Assign it to users
On the permission set, click Manage Assignments, then Add Assignments. Select the users who need the capability and confirm. Set an expiration date if the access is meant to be temporary.
- Verify the net access
Open one assigned user record and view the access summary, or use User Access Policies, to confirm the permission now resolves as enabled from the combination of their profile and this permission set.
Where you set Read, Create, Edit, Delete, View All, and Modify All for an object, plus field-level security for that object's fields.
The list of user permissions such as API Enabled, Manage Users, Author Apex, and View All Data that control tasks and features rather than records.
Optional licensing scope for the permission set. Leave it as None for a set that should apply across users regardless of their permission set license.
An optional end date on an assignment so a temporary grant lapses automatically instead of lingering.
- Permission sets only add access. To remove a permission a profile grants, change the profile or use a muting permission set in a permission set group, not the permission set itself.
- Object access without the matching field-level security still hides protected fields, and field access is useless if the user cannot reach the object at all.
- View All and Modify All ignore your sharing settings for that object, so grant them deliberately and to as few users as possible.
- Editing a profile changes access for every user on that profile, which is why a dedicated permission set is safer for a one-off grant.