As an admin user, even though you are able to change your own access level, it would be best to avoid experimenting with it. This is especially important if you own workflows. Changing your access level could lead to a miscommunication on the backend processes tied to your username.
For example:
- Any workflows you created which may be running in the background could fail. This is because a member or guest user does not have the requisite permissions to update the connection required for workflow runs.
- Any playbooks you created which may be running in the background could also fail. This can happen if a playbook is updating assets with explicit deny permissions.
- Additionally, you will lose access to the workflow, admin, and governance centers to make any modifications.
Atlan recommends creating a member or guest login with a dedicated email address for each and using them for testing views and permissions. This will help you accomplish the same goal while avoiding potential disruptions and leaving your admin access intact.