Service administrators are users that have unrestricted access to service configuration, can perform all service administrative tasks and all operations in Managed Domains. Service administrator operations do not pass security checks as their permissions are limited only by the permissions of the account specified for domain accessing.

Service administrator permissions allow to:

Security Roles assigned on service administrators do not limit their permissions. So, if you specify a user as a service administrator, the Security Roles that were assigned to this user cease to be effective, and this user gains unrestricted access to objects of Managed Domains and service configuration.

In the process of Adaxes service installation, the default service administrator is specified. The default service administrator cannot be removed or changed.

When two services share configuration, the information on service administrators is also shared, which means that every service gets the combined list of service administrators specified for each service. However, the default service administrator of one service can be removed from the list of service administrators in another service with which it shares configuration.

For example, if you have a service installed on 'serviceA.alpha.com' with the default service administrator ALPHA\Administrator, and then install a service on 'serviceB.beta.com', which shares the configuration with 'serviceA.alpha.com', and specify the default service administrator BETA\Administrator for this service, both services will have two service administrators: ALPHA\Administrator and BETA\Administrator. In this case, you can remove ALPHA\Administrator from the list of service administrators of 'serviceB.beta.com'. However, you cannot remove BETA\Administrator from the list of service administrators of 'serviceB.beta.com' as it is the default service administrator of this service. And therefore, in 'serviceA.alpha.com' service you can remove BETA\Administrator, but not ALPHA\Administrator.