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
From the Admin screen, you can access Nodes, Users, Roles, Teams, Two Factor Authentication, 2FA settings, and User Provisioning.
Nodes provide a method to organize your users, roles, teams and administrators into distinct groupings, similar to organizational units in Active Directory. The administrator can create nodes based on location, department, division or any other structure that makes sense for your organization. Nodes can have completely independent sets of users, role enforcement policies, administrators, and provisioning methods.
By default, the top-level node, or Root Node is set to the organization name, and all Nodes can be created underneath. Depending on your organization you may or may not need to set up nodes.
Small teams may not need multiple nodes and will be able to administer users, roles, and teams from the default root node only.
Larger teams may benefit from organizing by location or department across multiple nodes.
All employees or Users you choose to deploy Keeper to, will be responsible for managing their own encrypted vault. Whether users are manually created or provisioned automatically, their vault is protected by a Master Password which is used to encrypt and decrypt the user's data key which is then used to encrypt their data. We recommend separating your personal, private records from your business records by creating two separate user accounts. When enforcements are applied to the organization (such as Account Transfer privileges), users who have personal records mixed with business information risk having their personal information transferred.
Roles provide the organization the ability to define enforcements based on a user's job responsibility as well as provide delegated administrative functions.
Permissions for Administrators are also configurable here which toggle whether an Admin can manage nodes, users, teams, roles, SSO, AD Bridge, User Account Transfer and Run Reports.
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.
As you prepare to rollout Keeper to your organization, consider one of the following options when inviting users:
Access to additional Secure Add-On functionality can be accessed through the Admin Console side bar and includes: