1

Is it possible to create a sandbox, a user, limit that user's access to only that sandbox, and then later if needed, switch the user from the sandbox only access to production access?


UPDATE:

  • No, the data/configs/etc created by the user in the sandbox does not need to be pushed to production; different topic, really.
  • Yes, the user-profile data does need to move, meaning that there's no need for the user/admin to create/recreate user-data such as: role, password, email, etc.
  • When you mean switch, do you want the user created data to be moved over to the production box too? – Rao Apr 3 '14 at 21:06
2

No. Usernames have to be unique between production and sandbox orgs (but can be the same on pre-release orgs). So you'd be unable to do this with the exact same username.

You could create the user on the production org and keep it inactive. While creating a sandbox, the user will be copied to the sandbox and his name will be appended by ".sandboxname" to maintain uniqueness. You could activate the user on the sandbox, and after a while activate the user account on the production org, but they can't be the same login.

  • Just to be clear, it is okay for the user's email to be the same, but the username must be unique, right? – blunders Apr 3 '14 at 21:22
  • 2
    @blunders That's correct, the user's email can be the same across multiple orgs, but the username is unique. – Rao Apr 3 '14 at 21:30
0

Yes, the simplest way is once you created your sandbox, login to it, create this user and when needed create it also in production org. For the switch you'll need to activate or deactivate the user in each environment.

don't forget to add the ".sandboxName" to end of the username.

  • 1
    You will need to create a new user though. – Samuel De Rycke Apr 3 '14 at 21:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.