Does anyone have a checklist of the things we need to address before an Admin is deactivated to prevent any disruption? I know calendars will go away with their owners, an reports that run as the user, but is there anything else I may be forgetting. Also, will it effect Fusion scenarios in any way?
Hi
It’s a good idea to audit all objects owned by the admin using reports, this includes calendars, dashboards, Boards, Fusion scenarios, API keys, and any integrations. Once identified, make sure to transfer ownership of all critical assets (calendars, dashboards, Boards, Fusion scenarios, etc.) to an active user or service account.
Also, ensure you update or regenerate any API keys and integrations tied to that user, as these will stop working once the user is deactivated. Similarly, if Fusion connections were authenticated using their credentials, those will need to be reauthorized under a different user.
Additionally, review and reassign any work, approvals, or proofing-related responsibilities, and ensure licenses are adjusted if needed. Finally, don’t forget to remove the user from teams/groups and update admin role assignments to maintain proper access coverage.
This usually helps ensure a smooth transition without unexpected breaks in automation or reporting.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.