How to Copy Salesforce Permission Sets, Groups and Queues Between Users
Compare and selectively reproduce Salesforce user access while checking licences, direct memberships, and existing assignments.
Published by Cloud Exam Coach · · 5 min read
← Back to all learning resourcesCreate an approved access comparison
Start with the target role requirements and identify a suitable source user. Record only the assignments the target needs. A source user may have temporary or privileged access that should not follow a colleague into a new role.
Distinguish the access categories
Permission sets add permissions. Permission set groups bundle permission sets and may include muting. Public groups and queues serve different sharing and work-assignment purposes. A list of direct memberships is not a complete explanation of effective record access through roles, nested groups, and sharing.
Check licence compatibility first
Salesforce can reject an assignment that the target user licence does not support. Where a permission set group requires a permission set licence, assign the required licence first. Confirm available licences and the target profile before copying access; do not solve an incompatibility by granting an unnecessarily powerful profile.
Apply the reviewed differences
Use Salesforce User Cloner to compare supported source and target assignments and include only the approved items. Review the capabilities shown in the installed version; handle unsupported categories through Salesforce Setup. Preserve valid assignments already held by the target.
- For permission sets, use Manage Assignments on the relevant permission set.
- For permission set groups, use Manage Assignments on the group and confirm its licence requirements.
- For public groups and queues, inspect the configured membership in Setup and add only the intended target.
- Review each result and investigate errors before retrying.
Test effective access and record exclusions
Check that the target can perform representative tasks, access required records, and use the intended queue workflows. Also confirm that excluded sensitive capabilities remain unavailable. Record what was added, what already existed, and what was deliberately excluded; this supports a later review or removal of the new assignments.