The previous developer for my org, who built 100% ...
# general
a
The previous developer for my org, who built 100% of all our scripts, left last summer, and it broke a bunch of things because various integrations were tied to his user auth keys. My question is, would it be sensible to create a separate super admin user for all integrations and script ownership in order to avoid that happening again, or is there a better way?
n
I would recommend to have a separate user/employee record for the authentication tokens only.
Script owner doesn't really matter. It will not break the scripts. You can change the owner later on as well.
e
Always create an Integration role and an integration web services only user to create the consumer/access key tokens.
l
Will there by any problem if we transfer the integration role from one user to another?
e
You will need to create user access tokens for that user
l
But it wouldn't break anything as long as we redo the setup for the new user?
n
It will break the integration if you disable the access of the user who has left the company. When you generate new tokens, you will need to update it for all the integrations.
l
For next time, it might help to see all the customizations owned by inactive users which is something Flashlight by Strongpoint can show easily: https://www.strongpoint.io/flashlight-by-strongpoint