Admin deactivation

yes if your person has been authenticating their fusion connections as themselves, these will be an issue, as well as any Boards they have created.

Does this person have an API key by the way? Anywhere the key is being used will be at issue. For instance, you could be using it in an external lookup field. Or a powerBI/analytics team might be using it to pull data.

Hi ​@Tracy_Parmeter , great points from ​@skyehansen , she’s already covered some of the key areas. Adding a few more things you may want to consider before deactivating an admin to avoid any disruption:

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.