Users and Contacts

• Because all Salesforce usernames must be unique and reference a single org, usernames are modified to ensure uniqueness as they are copied.

  Each username is modified with these actions.

  • First, the sandbox name is appended to the username. For example, the username user@acme.com for a sandbox named test becomes user@acme.com.test.
  • If the resulting username isn’t unique, a second modification is performed in which some characters and digits are prepended to the modified username. This second modification results in a username such as 00x7Vquser@acme.com.test.

  When you log in with the modified username, you log in to the corresponding sandbox.

• When you create or refresh a sandbox, user email addresses are modified so that production users don’t receive automatically generated email messages from the sandbox. User email addresses are appended with .invalid. This modification makes sure that the system ignores these email addresses. For example, a user email of awheeler@universalcontainers.com in production becomes awheeler@universalcontainers.com.invalid when migrated to sandbox. If you want sandbox users to receive automatically generated emails as part of testing, you can correct the email addresses while logged in to the sandbox. Return email addresses set in users’ Email Settings in production aren’t appended with .invalid in the sandbox.
  

  Warning Sandboxes change Salesforce user email addresses, but don’t change other email addresses in Salesforce, such as email addresses in contact records. To avoid sending unsolicited email, manually invalidate or delete all email addresses in your sandboxes that don’t belong to users of the sandbox. When testing outbound email, change contact email addresses to the addresses of testers or an automated test script.
• Each sandbox user’s account email must be verified before that user's account can send email from Salesforce.

The copy process doesn’t copy all users or object data to Developer or Developer Pro sandboxes. For example, Customer Portal users and the Contact and Employee2 objects aren’t copied. The copy process does include the Customer Portal and Unified Employee licenses, so you can create Customer Portal users in Developer or Developer Pro sandboxes.

Copy Type	Includes Users with Unified Employee License	Includes Users with Customer Community License	Includes Contact Object	Includes Employee2 Object
Developer or Developer Pro copy
Partial copy without the Contact object selected
Partial copy with the Contact object selected
Full copy