Admin Access

Administrators who use the SafeLinx Administrator must authenticate by providing an administrator ID and password.

With SafeLinx Administrator, you can organize your SafeLinx resources into different organizational units (OUs). After you assign resources to specific OUs, you can specify the level of access that you want to grant each administrator to resource types in each OU.

For example, you might place users into OUs based on location and then grant administrators the access to manage users in certain locations only. You might grant one administrator the access to manage mobile devices and grant another access to manage MNCs. By planning the organizational structure of your resources, you can provide administrators with as much or as little access and capability as you want.

If you do not want to use OUs to control access to SafeLinx resources, you can define all your resources in the root OU. The root OU is created the first time you log on to the access manager.

When you log on to SafeLinx Administrator as the default SafeLinx Server administrator (admin), you have complete control (super user authority) over all resource types in all OUs. You can create administrators with different access to different types of resources. You can define at least one administrator other than the default administrator.

You can specify whether the default admin (admin) can log in remotely to the access manager by using the SafeLinx Administrator. To prevent remote access by the default admin, edit the Security page of the access manager properties and clear the check box Allow super user administrator IDs to log in remotely from SafeLinx Administrator. For more information about how to edit properties, see Editing resource properties.
Note: Linux administrators who log on using the operating system root ID have the same access to resources as the default administrator, including remote access.