What are Best Practices for Portal Administrator Accounts?
Our Portal is configured to use only SSO single sign-on for logins, and built-in user sign-ins are disabled. This has a nice benefit of allowing users to sign in to maps and apps quickly without having to think about clicking a sign-in option (for example, if built-in logins are enabled, users will try to enter their SSO credentials into the built-in field and it will fail).
I have my own personal SSO account enabled as a Portal Administrator. This allows me to quickly make changes to maps, apps, members, Groups, etc. However, a downside of this is that my user doesn't "see" maps and apps in the same way as normal users because of my Administrator Role. On more than one occasion, I have loaded a map/app and it works just fine, but standard users might see a layer permission issue or related problem.
Is it possible to use only SSO sign-in, but still be able to login as a built-in Administrator user? For example if I demote my personal SSO to a Publisher or similar role, but have a built-in Administrator user that i can use for Portal administration tasks?
