When you first log in to the Admin Console, you will land on the Dashboard which will provide an overview of high level data on your user activity and overall security status.
The Dashboard provides oversight of the following:
Top Events and link to Timeline Chart
Security Audit Overall Score
BreachWatch Overall Score
User Status Summary
The Admin tab is where majority of your set-up and user deployment will take place. Here, is where you can access Nodes, Users, Roles, Teams and Two-Factor Authentication Settings.
As a first step, we recommend uploading your company logo to the vault and customizing the email invitation that will invite your employees to create their Keeper Vault. These configurations are highly recommended as they have shown to help with quick user adoption of Keeper's software.
Configuration then click
Edit next to "Company Logo" to upload your image file.
Edit next to Email Invitation, then toggle "Send Custom Email Invitations" on.
The email invitation template supports customization of the following four attributes:
Download Button Text
Once you have finalized your changes, click
Save . When you are ready to add your users, they will receive your customized invite similar to the one below.
In Keeper's architecture, Roles allow you to define enforcement policies based on a user's job responsibility as well as provide delegated administrative functions. The number of roles you create is a matter of preference and/or business need.
Nodes are used to organize your users into distinct groupings, similar to organizational units in an Active Directory. You can create nodes based on location, department, division or any other structure. Smaller organizations may choose to administer Keeper as single level, meaning no additional nodes are created. In this scenario, all provisioned users are accessed from the default "Root Node".
We recommend you create a secondary Keeper Administrator as soon as possible. At its simplest configuration, the Keeper Administrator role is applied to the initial administrator who has set up the Keeper account for the organization as well as any other user you grant full admin rights. We strongly recommend you add a second user to the Keeper Administrator role in case one account is lost or no longer accessible.
Admin > Users > + Add Users enter the user's full name and email address, then click
Admin > Roles > Keeper Administrator and clicknext to Users
Select the new user from the list and click
OK to finish.
Account Transfer is an optional, by highly recommended feature that should be configured by the Keeper Administrator during the initial deployment phase of the Keeper rollout. The reason for this is because Account Transfer relies on the sharing of encryption keys between users that have rights to perform the transfer. The exchange of keys occurs when the user logs into their vault to retain Keeper's Zero-Knowledge infrastructure. Therefore, the Account Transfer setup must be configured prior to the user's account being transferred.
First you will need to enable the Transfer Account permission for the Keeper Administrator Role. In the case that an employee leaves the company, all of their records and data will be preserved and transferred to a specified user as determined by the Keeper Administrator.
Admin > Roles > Keeper Administrator
Under Admin Permissions, hover over your company name and click
Check the box next to "Transfer Account" and click
As a second step, Enable Account Transfer for the Keeper Administrator Role. This will allow the vaults of you and any delegated admins, under the Keeper Administrator role to be transferred.
Admin > Roles > Keeper Administrator
From the Transfer Account tab, toggle "Enable Account Transfer" on then click
Roles allow you to define enforcement policies based on a user's job responsibility as well as provide delegated administrative functions.
You will need at least one role defined for your users, but you can create as many as you would like depending on the structure of your organization. Roles can be created to support a variety of policies depending on what enforcements should be applied to a user based on their position (e.g. Administrators, Executives, Managers, Staff, and Contractors). For smaller organizations, Keeper recommends you create a default, "General Employee" role.
Admin > Roles > + Add Role
Select the Node you want to add the Role to, enter the name of the role and click
Nodes are used to organize your users into distinct groupings, similar to organizational units in an Active Directory. You can create nodes based on location, department, division or any other structure.
Smaller organizations may choose to administer Keeper as single level, meaning no additional nodes are created. In this scenario, all provisioned users are accessed from the default "Root Node" (e.g. ACME Co.).
Admin > + Add Node
Enter the name of the Node then click
Add Node to finish.
At any time, you can change which node you are viewing by navigating to or selecting the Nodes on the far left Node pane. To navigate to the root node or top level, select your business name (e.g. ACME Co.) in the navigation tree.
To ensure that a certain role is applied to all imported users, enable the “Set as Default Role for Node and Sub Nodes” setting. This will automatically assign new users that are added to a Node or Sub Node to a specified role.
Admin > Roles select the target role then check the box next to "Set as Default Role for Node and Sub Nodes".
Role-based Access Controls (RBAC) provide your organization the ability to define Enforcements Policies based on a user's job responsibility as well as provide delegated administrative functions.
Enforcement Policies offer a wide-range of control features that are organized into the following categories:
Two-Factor Authentication (2FA)
Sharing & Uploading
Admin > Roles select a role then click
A dialogue box will appear where you can configure the Enforcement Policies that will be applied to the selected role. Click
Done when finished.
Business customers can seamlessly deploy Keeper to their users using two different methods. Admins can either manually invite individual users or bulk import users via a CSV file.
Admin > Users > + Add Users
Select the Node you would like to add the user to, enter their Full Name and Email Address then click
Admin > Users > + Add Users
Select the Node you would like to add the users to then simply drag and drop your formatted CSV file of users or click
Browse Files to upload the file from your local device (the Role field is optional). To learn more about formatting your CSV file, click here.
Review the user details and click
Add to complete the import.
Next, we encourage you to create Teams. The purpose of creating teams is to give users the ability to share the records and folders within their vaults with logical groupings of individuals. The administrator simply creates the team, sets any Team Restrictions (edit/viewing/sharing of passwords) and adds individual users to the team. Teams can also be used to easily assign Roles to entire groups of users to ensure the consistency of enforcement policies across a collective group of individuals.
Admin > Teams > + Add Team
Select the Node you want to add the team to then enter the name of the team and click
You can then set the following team-level restrictions:
Disable record re-shares
Disable record edits
Apply privacy screen
Clickto add individual Users and Roles to the team.
As a final step to further enhance your security practices, we recommend that you require the use of Two-Factor Authentication across your organization. This role enforcement can be enabled within each role's Enforcement Policy settings.
Admin > Roles select the target role and click
Toggle "Require the use of Two-Factor Authentication" on.
Set your platform-specific enforcements, enable the desired 2FA methods then click