User management in Management Console

Users (or user accounts) are required for access to the Console and other Cloud services.

• There are several user roles to choose from. They make it possible to differentiate access to data and features within a company.

• Customers can have an unlimited number of users.

User roles

The following user roles are available:

• SuperUser
• Administrator
• Manager
• Operator
• Supporter

Security Officer is an additional setting which can be applied to certain roles to provide additional access to generate a passphrase:

• SuperUser
• Administrator
• Manager
• Operator

Key

The following icons indicate availability:

Key	Status	Description
	Available	Is available for all
	Limited Availability	Is available for with limitations (see Note for additional information)
	Read Only	Is available in read only mode
	Not Available	Is not available

Please see the table below for access permissions available to each of the roles.

Task	SuperUser with security officer	SuperUser	Administrator with security officer	Administrator	Manager with security officer	Manager	Operator with security officer	Operator	Supporter
Adding devices					(Note) Self-managed installation only	(Note) Self-managed installation only
Export of monthly device statistics
Generating passphrases Passphrases are used instead of Encryption Key/Security Code during the re-installation of automatically deployed devices, for the cleanup of backup data sources and for the addition of devices to the Recovery Console.
Launching backup devices remotely
Recovering data in Backup Manager
Recovering data in Recovery Console		(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.		(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.		(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.		(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.
Recovery Testing		(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.				(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.
StandBy Image		(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.				(Note) If the device uses Passphrase-based encryption, this user level does not have access to generate these and so will not be able to add the device to the Recovery Console. If the device uses a Encryption Key/Security Code, this user level will be able to proceed with the recovery via Recovery Console.
Recovery Locations
Managing backup profiles Feature available to resellers and end-customers only
Managing contact notes
Managing contacts Names of customer representatives and their contact details
Managing customers
Managing devices All features except adding devices and generating passphrases
Managing Microsoft 365 domains		(Note) Cannot delete services or delete account/site backup history	(Note) Cannot delete services or delete account/site backup history		(Note) Cannot delete services or delete account/site backup history		(Note) Cannot delete services or delete account/site backup history
Managing retention policies
Managing security officers Flagging SuperUsers as Security Officers and removing the flag
Managing users All features except for managing security officers
Managing API users
Managing notifications
Managing views
Sending remote commands to devices

Adding users

You can add new users for your own company and for your customers. Here are steps to follow:

1. In the vertical menu, click Users

2. Click Add user

   

3. Fill out the fields as fully as you can

   

4. Ensure you select Security Officer as this user role grants permission to request a passphrase
5. Click Save to apply the changes

The owner of the new user account will get an email notification with a password setup link.

Adding API users

API users can access Cove's API but are restricted from logging into the Cove console.

You can add API users for your own company and for your customers. Here are the steps to follow:

1. In the vertical menu, click Users and then click API users. Click Add API user

   

   You can navigate to the standard users dashboard by clicking User Management in the vertical menu.

2. Enter the fields in Add API User window

   

3. Ensure you select Security Officer as this user role grants permission to request a passphrase

4. Click Save and continue and copy the token in the Copy token window through Copy token to clipboard

   

5. Click Download token to download the token

6. Click Copy and close to add the API user

This token is only visible once, so please save it securely. If you miss this step, you will need to delete the user and create a new one.

Editing users

You can change any of the settings configured for a user except for the log-in name. Here is how to:

1. Click the three dots under Actions next to the name of the user that you want to edit and click Edit user

   

2. Edit the settings as required and click Save to apply. You can click the icon next to the Customer, Email, and Name to copy to clipboard

   

Under Additional settings, API access can be enabled and disabled for users through the edit user functionality.

Editing API users

1. Click the three dots under Actions next to the name of the user that you want to edit and click Edit user

   

2. Edit the data as required and click Save changes to apply. You can click the icon next to the Customer and Login name to copy to clipboard

   

Removing users

Here is how to remove a user from the system:

1. Click the three dots under Actions next to the name of the user that you want to delete and click Delete user

   

2. Click Delete to delete a specific user, else click Cancel

   

After a user is removed, it will not be possible to access the Console with the deleted user account. All people logged in under that account will be logged out within the next 15 minutes.

Removing API users

1. Click the three dots under Actions next to the name of the user that you want to delete and click Delete user

   

2. Click Delete to delete a specific API user, else click Cancel

   

After an API user is removed, it is not possible to access Cove APIs with this user.

Managing security officers

The first SuperUser who logs in to the Console is immediately flagged as a security officer. Only security officers can manage other security officers including themselves.

To add a user with the security officer permissions, do the following:

1. Log in to the Management Console as a user with security officer permissions
2. Navigate to the User Management module
3. Click Add user
4. Set the user role to SuperUser, Administrator, Manager or Operator

   

5. Select the Security officer checkbox
6. Click Add

You can also grant or remove security officer permissions to existing SuperUsers if necessary (see Edit user dialogue).

Each customer of the reseller or end-customer level must have at least 1 security officer. You cannot delete the last security officer.

Single Sign-On

Users log into the Management Console through a Single Sign-On service.

Please visit N-able Login in Management Console for further information.