Unitrends systems are managed and monitored from the Administrator Interface (AI). Based on the credentials provided, user’s privileges can be controlled to allow monitor or management capabilities for one or more systems.
By default, a superuser named root is created on the system. You should change the password of the root user (the system superuser) to tighten security.
User accounts can only be used to access the system for which they were created. Users are not shared across Unitrends systems. To log in to another system, the user must be created directly on that system or set up for that system using Active Directory authentication. See About Active Directory authentication for information.
User actions are logged in the system and can be viewed in the Audit History report. For details, see Audit History Report.
1 | In the Setup Wizard Add and Configure system users step, check the Do you want to add additional administrator users box, or select Settings > Customers, Locations, and Users > Users. |
2 | Click Add User. |
3 | Enter a username in the Username field. |
4 | Enter a password in the Password and Verify Password fields. Passwords may contain upper and lower case letters, numbers, and special characters with the exception of a space and an equal sign (“=”). |
5 | If desired, check Superuser. |
Note: If you are using Navigation grouping, be sure the user has Manage level privileges. For details, see Navigation grouping.
• | A superuser has privileges to perform all operations provided by the Administrator Interface for any system, at any customer location defined in the Navigation pane. |
• | Regular users are non-superusers that are added to the system to allow specific capabilities to manage one or more systems in the Navigation pane. |
• | For superusers, no further configuration is needed. Click Next to save the settings and continue with the Setup Wizard, or click Confirm to save settings in the Users subsystem. |
6 | For regular users, continue with this procedure to add privileges. |
One or more privileges must be added to create the overall scope and access level for the regular user. Log in is prohibited if no privileges are set for regular users.
7 | Click Add Privilege and modify settings as desired. Define a privilege level for each customer, location, and system. See descriptions of each privilege in the tables below. |
8 | Click Confirm to save the settings and Next to continue with the Setup Wizard, or click Cancel then Close to exit without saving. |
Privilege levels are given here.
Description |
|
---|---|
None |
The user cannot access the customer, location, or system. |
The user is only able to view the status of operations, such as backups or replication, and run reports. The user cannot start backups, restores or configure the system in any way. |
|
The user can view statuses and reports, start backups, and perform other management tasks, such as adding or modifying clients and retention settings. They can also view running jobs or processes, but cannot create or modify users other than modifying their own user account password. |
|
In addition to monitoring and managing systems, the user can add, edit, or delete customers or customer locations, and add, edit, or delete users. Because administrators can create customers and locations, they can also assign systems to different customers and locations in the navigational tree (using Settings > System, Updates, and Licensing > Grid Management). |
In addition, regular user’s privileges may be defined at various levels of breadth or scope.
Privilege scope |
Description |
---|---|
The most general privilege scope. The privilege level applies to all systems that are associated with all of this customer’s locations. By default, systems are assigned to the Default Location for the Default Customer. |
|
The privilege applies to all systems that are associated with this location for a selected customer. By default, systems are associated with the Default Location for the Default Customer. |
|
The most finely-grained privilege scope. The privilege level applies to a particular system at a defined location for a defined customer. |