Deployment Step: Users

Updated 20 hours ago by David Venegas

This article is part of the Deployment Steps.

The Users deployment step lets you deploy users from one Org to another.

Note:

  • Both standard and custom fields of users are deployed.
  • Optionally you can include User Territory assignments and Permission Sets as part of the deployment.
  • For users with a manager and/or delegated approver assignments, these are mapped across as part of the deployment.
  • Only internal users (UserType=’Standard’) will be retrieved.
Territories and Permission Sets

When transferring territories and/or Permission Sets, these need to have been deployed already in a previous step in order for the user step deployment to succeed. Copado will deploy users automatically and then associate the corresponding Territories and/or Permission Sets with the User. If the users are not activated, Permission sets won't be assigned.

Manager and Delegate Approver

When transferring users with an associated Manager and/or Delegated Approver, Copado will deploy the users and associate the Manager and/or Delegated Approver with the deployed user automatically. Please note that the related User must also be queried and be present in the deployment. This may all be done within 1 step and does not require a multi-step deployment as with Territories and Permission Sets. In order for Permission Sets to be assigned, the users must be deployed as ‘Active’.

Suffix Information

During the deployment Copado will append a suffix to the Username, email and the Community nickname. If no suffix is specified, nothing will be appended. If a ‘From Suffix’ is specified and not a ‘To Suffix’, then the text ending with the ‘From Suffix’ will be replaced with the ‘To Suffix’.

E.g. a deployment from sandbox called "UAT" to Production The From Suffix will be set to "UAT" and the ‘To Suffix’ will be left blank. John Smiths username (e.g. Jsmith@company.com.uat will become Jsmith@company.com. Bear in mind that User deployments must run on a single destination Org deployment.

Example

Sandbox named, ‘UAT’ -> Production

Email

jsmith@company.com.UAT -> jsmith@company.com

Username

jsmith@company.com.UAT -> jsmith@company.com

CommunityNickname

JohnSmithUAT -> JohnSmith


How did we do?