Include the Internal (Full Access) Cloudworks account in Users for easy permissions management

Stacey_Gibbens

I have recently learned that the reason some of our Cloudworks integrations were not running properly is because the Internal (Full Access) account used by Cloudworks was not assigned the appropriate list-level security. The following Anapedia article describes the requirement: Internal (Full Access) | Anapedia

The idea is for the Internal (Full Access) account to be listed in the Users tab by default to make it clearly obvious and easy to understand that this account must also be provisioned AND make it easy to manage by the Workspace Admin.

Hiding the Internal (Full Access) account provisioning within each list with Selective Access applied prevents the Workspace Admin from easily viewing and understanding the cause of an integration failure. The name of the account "Internal (Full Access)" indicates a God account (and it acted this way prior to about June 2024). After about June 2024, the selective access restriction was changed and it was very unclear to many people why this happened. Displaying the Internal (Full Access) user as a default system account showing in the Users tab would surface this provisioning requirement and make it much easier for Workspace Admins to manage their integrations successfully.