> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/quick-start-guide-for-small-business-teams.md). # Keeper for Teams and Small Business This quick start guide will help get your small business team up and running with Keeper Business in just minutes.

## Admin Console Overview 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 Score * BreachWatch Score * User Status Summary

The Admin tab is where the 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, Approvals and Provisioning.

## Customization & Branding As a first step, we recommend uploading your organization logo to your users' vaults and customizing the email invitation that will invite them to create their Keeper account. These customizations are highly recommended as they have shown to help with quick user adoption of the Keeper platform.

Upload Your Organization Logo

Navigate to **Custom Branding** in the left navigation menu and click **Edit** beneath "Custom Branding" to upload your organization logo.

Create a Custom Email Invitation

Navigate to **Custom Branding** in the left navigation menu and click **Edit** beneath "Email Invitations" and toggle "Send custom email invites" on.

Admin Console > Custom Branding > Email Invitations

The email invitation template supports customization of the following four attributes: * Subject * Message Heading * Message * Account Setup Button Text {% hint style="info" %} The body of the message supports plain text as well as basic markdown syntax {% endhint %}

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 example below.

## Initial Configuration Steps There are a few configuration steps we recommend you take prior to deploying Keeper organization-wide. Before you do that however, you will first want to have a general understanding of Keeper's organizational structure. **Organization Overview** In Keeper's architecture, **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" (your organization name). **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. By default, every new Keeper tenant will have a "Keeper Administrator" Role and a "All Users Role". ### Create a Secondary Keeper Admin We strongly recommend you create a second user within the Keeper Administrator Role as soon as possible in case one account is lost or no longer accessible. At its simplest configuration, the Keeper Administrator role is applied to the initial administrator who has set up the Keeper account for the organization. To add a Secondary Admin to your Keeper account, you will first need to add them as a User. From the **Admin** section of the console click **Users > Add User** and enter the their full name, email address and job title (optional) then click **Add**.

Next you can add the new user to the Admin Role. Select **Roles > Keeper Administrator** **> Add User**.

Select the user(s) you would like to add from your user list and click **Add User**. This will generate an email inviting the user(s) to setup their Keeper account.

### Setup Account Transfer Account Transfer allows a Keeper Administrator to transfer records and data from one user to another, should an employee leave the company for example. We highly recommend you enable this policy for the Keeper Administrator prior to deploying Keeper organization-wide. Setting up Account Transfer is a 2 step process: 1. Ensure the "Transfer Account" permission for the Keeper Admin Role is enabled (this permission is enabled by default for the Keeper Administrator role for new tenants). 2. Turn on the "Enable Account Transfer" Enforcement Policy for the Keeper Admin Role {% hint style="warning" %} Account Transfer must be enabled prior to a user's account being transferred. {% endhint %}

Enable the Transfer Account permission

Click **Roles > Keeper Administrator**. ![](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2Fr8n6bjovemergGfrqQnQ%2FScreenshot%202026-09-03%20at%207.53.36%E2%80%AFAM.png?alt=media\&token=b7a367e6-caab-4c9d-a2d1-65353e2eb0dd) Select the "Administrative Permissions" tab and click the **gear icon**. ![](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2Fbi6y5uT9g6estGNUbiir%2FScreenshot%202026-09-02%20at%209.31.28%E2%80%AFAM.png?alt=media\&token=af2027c0-08b4-439f-9d6c-6fae31d34eb9) Confirm the box next to "Transfer Account" is checked and click **Save**. ![](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FDIQSMMsFBrOWnzTrzDih%2FScreenshot%202026-09-01%20at%203.04.40%E2%80%AFPM.png?alt=media\&token=cd436f40-2a05-49d8-b822-f9679f8f9ac1) {% hint style="info" %} To learn more about Account Transfer, click [here](/enterprise-guide/account-transfer-policy.md) {% endhint %}

Turn on the Account Transfer Enforcement Policy

As a second step, turn on the "**Enable** **Account Transfer"** enforcement policy for the Keeper Administrator Role. This will allow the vaults of you and any delegated admins, under the Keeper Admin role to be transferred. Click **Roles > Keeper Administrator > Enforcement Policies**. ![](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FdY9ax5cFVGFrr3gSr6Ox%2FScreenshot%202026-09-01%20at%202.35.31%E2%80%AFPM.png?alt=media\&token=a8580d42-52c3-4c77-b482-2b7f2fea0794) From the "Transfer Account" tab, toggle "Enable Account Transfer" on. Next, from the dropdown menu, select the role that can perform the account transfer. In this case, select Keeper Administrator and click **Save**. ![Enable Transfer Account](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FIQI1QHVxv8X0RsyQYJBz%2FScreenshot%202026-10-02%20at%2011.14.35%E2%80%AFAM.png?alt=media\&token=3fc60804-d7fc-4dec-b69c-26fbac47db90) {% hint style="info" %} Users will be notified when account transfer is enabled and must acknowledge the organization's ability to transfer records. This consent is required only once upon login. {% endhint %}

### Create Nodes 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 (your organization name).

Create a new Node

From the Admin section, select the **overflow menu icon (three dots)** next to the Root Node and click **Add Node**. ![Add Node](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FuCFPGjq8QmEv1I0ErRFU%2FScreenshot%202026-09-02%20at%209.37.39%E2%80%AFAM.png?alt=media\&token=ee281c4e-d440-45ed-a4cb-947fb9530c34) Enter the name of the new Node then click **Add Node.** ![Name and Location of Node](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FjNmQOLoP41w1Efed1XCn%2FScreenshot%202026-09-02%20at%209.50.14%E2%80%AFAM.png?alt=media\&token=f37bd9b6-cfcc-4df6-a2dd-99535b5f3c44) You can switch nodes or return to the top level/root node (your organization name) at any time from the Node dropdown menu.

{% hint style="info" %} To learn more about Nodes, click [here](/enterprise-guide/nodes-and-organizational-structure.md). {% endhint %}

Set Default Role for Node & Sub Nodes

To ensure that a certain role is applied to all added 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. To enable this setting, select **Roles** then select the target role and check the box next to "Set as Default Role for Node and Sub Nodes". ![Set Role as Default](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FEtCtZj5cjaNrAfOtgW6J%2FScreenshot%202026-09-02%20at%2010.02.03%E2%80%AFAM.png?alt=media\&token=359aef54-90d2-4eb8-b414-4e316eaacdaa)

### Create Roles 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 has created a default "All Users" role. To add a Role, click **Roles > Add Role**. ![Add a Role](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FCH45ymcjb6A8yiyq8Wp5%2FScreenshot%202026-09-01%20at%203.10.36%E2%80%AFPM.png?alt=media\&token=bad33f83-7ccf-4272-9209-b0931c8efef4) Select the Node you want to add the Role to, enter the name of the Role and click **Add**. ![Add a Role to a Node](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2Fi5cOZhxXMYxV2Q8rJmAM%2FScreenshot%202026-09-01%20at%203.19.10%E2%80%AFPM.png?alt=media\&token=cc8e15c0-91ea-43f2-927b-7863b4630f09) {% hint style="info" %} For more detailed information about Roles, click [here](/enterprise-guide/roles.md). {% endhint %} ## Set Enforcement Policies Role-based Access Controls (RBAC) provide your organization the ability to define granular **Enforcements Policies** based on a user's job responsibility and defined Role as well as provide delegated administrative functions. Enforcement Policies offer a wide-range of control features that are organized into the following categories: * Login Settings * Two-Factor Authentication (2FA) * Platform Restriction * Vault Features * Record Types * Creating and Sharing * Import and Export * KeeperFill * Account Settings * Allow IP List * Privileged Access Manager * Transfer Account To set Enforcement Policies for a role, click **Roles**, select the target role then click **Enforcement Policies**. ![](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FvepX5kd24umQtMhn3Mm6%2FScreenshot%202026-09-01%20at%202.35.31%E2%80%AFPM.png?alt=media\&token=a85b9ed5-943c-4d2a-81d9-b1b336143066) Next you can configure the Enforcement Policies that will apply to the selected role. Click **Save** when finished.

{% hint style="info" %} For more information on Keeper's many Enforcement Policies, click [here](/enterprise-guide/roles.md#role-enforcement-policies). {% endhint %} ## Enable Two-Factor Authentication A highly recommended step to further enhance your organization's 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. Click **Roles** and select the target role, then click **Enforcement Policies**

Within the "Two-Factor Authentication" section, toggle "Require the use of Two-Factor Authentication" on.

Set your platform-specific enforcements, enable the desired 2FA methods then click **Save**.

## Deploy Keeper to Your Employees 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. Advanced deployment options are also available.

Manual User Provisioning

Click **Users > Add User**.

Select the Node you want to add the user to, enter their full name, email address and job title (optional) then click **Add**.

{% hint style="info" %} This will generate an email inviting the user to setup their Keeper account. {% endhint %}

Bulk User Import

Click **Users > Add User**.

Select the Node you want to add the users to then simply drag and drop your formatted CSV file of users or click **Browse for File** to upload the file from your local device (the "Role" field is optional). To learn more about formatting your CSV file, click [here](/enterprise-guide/user-and-team-provisioning/manual-provisioning-through-admin-console.md#bulk-user-import). ![Bulk Import](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FBZWytQfHOen6cIOfcJLZ%2FScreenshot%202026-10-02%20at%2011.04.24%E2%80%AFAM.png?alt=media\&token=7990a139-93c8-4f1b-a94a-ef311aca202c) Review the user details and click **Add** to complete the import. ![Review User Import Details](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FhFG0Kp1IKkBHqq5oNsoS%2FUntitled%20design%20\(76\).png?alt=media\&token=d2b1d292-7954-4053-bd11-96c639168855) {% hint style="info" %} This will generate an email inviting the users to setup their Keeper account. {% endhint %}

Advanced Provisioning Methods

Keeper integrates with any SAML 2.0 identity provider for just-in-time provisioning including: * Entra ID / Azure AD * Okta * Google Workspace * Microsoft AD FS * Amazon AWS * Auth0 * Centrify * Duo SSO * F5 * OneLogin * Ping Identity * PingOne * Rippling * SecureAuth * Shibboleth * JumpCloud * HENNGE * CloudGate UNO * Any other SAML 2.0 identity provider {% hint style="info" %} To learn more visit the User and Team Provisioning guide [here](/enterprise-guide/user-and-team-provisioning.md). {% endhint %}

## Teams 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 Keeper Admin simply creates the Team, sets any Team restrictions (edit/viewing/sharing of records) 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. Select **Teams > Add Team**.

Select the Node you want to add the team to then enter the name of the Team and click **Add Team**. You can then set the following team-level restrictions: * Disable record re-shares * Disable record edits * Apply Privacy Screen Click **Add User** to add individual or multiple users to the Team. {% hint style="info" %} Team-to-role mapping allows organizations to assign users directly to Teams that can be assigned custom Roles. With team-to-role mapping, a user who is a member of a team that is assigned to a role, will assume the enforcements of the given role. It's important to note, that Keeper implements least-privileged policies, so when a user is a member of multiple roles or teams, their net policy is most restrictive, or least privileged. To learn more about Teams and team-to-role mapping, click [here](/enterprise-guide/teams.md). {% endhint %} ## Reporting & Alerts Reporting & Alerts makes it easy to see Top Events ranging from opened records, logins, and failed login attempts. Reports are fully customizable by admins of your choosing, with parameters such as dates, event types, users, and nodes, all fully under your organizations control, allowing for comprehensive monitoring that contributes seamlessly to your compliance goals.

Reporting

The Reporting tab allows admins to generate and filter activity reports by date, event type, user, and node, supporting a comprehensive audit trail for compliance monitoring.

Alert Monitoring

The **Alerts** tab provides an overview of record sharing, logins, and detected high-risk events, allowing you to take action when necessary. ![Event Alerts](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FZtEEZHSRfOuD45ppkwhe%2Funknown.png?alt=media\&token=1dcd439d-2966-43ba-b7b4-7b22b5c2ab14)

External Logging

Keeper's External Logging integrates with dozens of compatible platforms, from CrowdStrike to IBM QRadar SIEM, allowing you to monitor all your security data in one place. ![External Logging Integrations](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2Fg5Sp5LAGtS4K8hSfKNOY%2Funknown.png?alt=media\&token=32282cc9-3f1f-4ccc-ad0b-8ae19f925a25)

## Risk Management The Risk Management Dashboard provides you with a high-level overview of security risks such as weak and reused passwords and an overall vault health score per user. The dashboard here complements the security overview seen in the Admin Console Dashboard. ![](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FREyMap769IQirVWxFCpw%2FScreenshot%202026-10-02%20at%203.12.42%E2%80%AFPM.png?alt=media\&token=5a856e5a-392d-4c5a-a0ff-5f9d03ed5280) {% hint style="info" %} ## To learn more about the Risk Management Dashboard, [click here](/enterprise-guide/risk-management-dashboard.md). {% endhint %} ## Compliance Reports Compliance Reports allows your administrators to generate reports on user access and record permissions. This is essential for auditing across nodes, roles, and teams while upholding your organizations compliance standards.

To create a new report, click **New Compliance Report** and apply your desired criteria filters including node, job title and records.

From this screen you can edit the search criteria and data filters to easily create or locate desired reports.

## **BreachWatch** BreachWatch monitors your business's credentials against known dark web data and notifies you of any suspected leaks. To view breach statuses across your organization, navigate to BreachWatch in the Admin Console's left navigation bar. If users have "At Risk" or "Ignored" passwords, the Keeper Administrator can contact the user and request they resolve the risk by changing their password at the affected side and updating the corresponding record. ![BreachWatch Dashboard](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FAGjv29ImvZN3Aa46LgLN%2FScreenshot%202026-10-02%20at%203.11.40%E2%80%AFPM.png?alt=media\&token=e089f387-3177-4a19-a2ab-9e6a45812035) {% hint style="info" %} End-users also receive notifications within their vaults when BreachWatch detects compromised credentials, alerting them to at-risk records. {% endhint %} ## **Integrations** Keeper supports seamless integration with the platforms your organization already relies on. This includes identity governance tools like SailPoint for automatic user provisioning, directory sync and Single Sign-On via Azure Active Directory, Google Workspace, and Okta — allowing employees to access Keeper with their existing company credentials. Keeper also integrates with Slack for real-time notifications and collaboration, SIEM platforms such as Splunk, Microsoft Sentinel, and CrowdStrike for security event monitoring, and is available across all major browsers via the KeeperFill extension, as well as iOS and Android mobile apps. For a full list of supported integrations, refer to the admin console section below, or visit: .

Integrations are now directly accessible from the Admin Console. Here, Administrators of your organization can browse available extensions, purchase integrations, and launch them without having to utilize external tools.

## Support For additional assistance, Keeper's support team is available to help your organization every step of the way. Submit a support ticket at keepersecurity.com/support or email .

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keeper.io/enterprise-guide/quick-start-guide-for-small-business-teams.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.