Creating Vault Records
A Keeper record can be any password, file or secret information that is stored in your encrypted vault. When a new user signs up for Keeper, they are walked through a step-by-step guide to import existing passwords from their web browser, other password manager or file upload. They will also be walked through the process of creating records manually through their desktop computer.
Users can create new vault records many different ways including:
Manual creation on the Desktop App, Web Vault, Browser Extensions or Mobile App
Import from another password manager like Keepass, LastPass, Dashlane or 1Password
Import from a .CSV flat file
Automated LastPass transfer
Command-line and automated SDK
Keeper's Import Tool will seamlessly import passwords that are stored in Chrome, Firefox, Edge and IE web browsers on your computer. From the Web Vault or Desktop App, click your account email address, then select Import. You will be then prompted to download Keeper's Import Tool.
Keeper support drag-and-drop import of files from other password managers or text files. From the Web Vault or Keeper Desktop app, select Settings > Import and then select the password manager you'd like to import your passwords from. Click View Import Instructions for step-by-step instructions to generate the proper file format from the original password manager. Once the file has been created, drag-and-drop it into the "Drop a File Here" field.
Keeper's Desktop Application supports an automated transfer of vault records from LastPass to Keeper. To perform an import, follow these steps:
Download the Keeper Desktop App from: https://keepersecurity.com/download
Login to Keeper Desktop using your Master Password.
Click on your account email address in the upper right-hand corner.
Click Settings > Import.
Choose LastPass.
Input your LastPass Email and Password and click Next.
File Format: Folder, Title, Login, Password, Website Address, Notes, Shared Folder, Custom Fields
To specify subfolders, use backslash "\" between folder names
To make a shared folder specify the name or path to it in the 7th field
Example 1: Create a regular folder at the root level with 2 custom fields
My Business Stuff,Twitter,marketing@company.com,123456,https://twitter.com,These are some notes,API Key,5555,Date Created, 2018-04-02
Example 2: Create a shared subfolder inside another folder with edit and re-share permission
Personal,Twitter,craig@gmail.com,123456,https://twitter.com,,Social Media#edit#reshare
In the preview screen, select the column header above each line to map the columns to the Keeper field.
The Keeper Commander SDK provides command-line or scripted capabilities to import records and folders into your Keeper Vault. Supported import formats are JSON, CSV, and Keepass.
JSON import files can contain records, folders, subfolders, shared folders, default folder permissions and user/team permissions.
CSV import files contain records, folders, subfolders, shared folders and default shared folder permissions.
Keepass files will transfer records, file attachments, folders and subfolders.
Most features available in the Keeper Admin Console are available through Commander's interactive shell and SDK interface. For more information, go to Keeper's Github Repository.
Learn more about Keeper Commander at https://github.com/Keeper-Security/commander
From any Keeper Vault application, select Create New > Record to add a record. When creating a record, you may select the Dice icon to generate a strong, unique password. Once you have entered the details of your records, click Save to finish.
Using the password generator feature will NOT automatically change the website's existing login password. You still must visit the corresponding website's "Change Password" form to update the old password to match the new, stronger password.
The Keeper Browser Extension for Chrome, Firefox, Safari, Edge, Opera and Internet Explorer browsers can be used to dynamically add records to your vault and Autofill passwords.
To download KeeperFill for your browser, visit: https://keepersecurity.com/download.html
Create New records From any website login screen, select Create New Record and then fill in the appropriate fields. Select the check mark to save the record and autofill the login and password.
Prompt to Login & Fill If you're logged out of Keeper, you'll be reminded to sign in to Keeper when visiting a website login screen. When visiting a website login screen, Keeper will ask you to automatically login with your saved password.
Prompt to Change Password KeeperFill makes it easy to change your passwords. When a user visits a site's "Change Password" form, you will receive a prompt from Keeper asking if you would like help changing your password. By clicking Yes Keeper will run a wizard that walks you through a few quick steps to change your password and simultaneously update the record in your vault. These steps will include a series of prompts detailing the following actions:
Autofill your old/current password
Automatically generate and autofill a new secure password
Confirm the changes and save them to your vault
A Keeper record is made up of the following fields:
Title
Login (Email or Username)
Password
Website Address - This field is required to Autofill forms on websites. For security reasons, the website address (e.g. google.com) must match the website that you are visiting.
Custom Fields - Creating Custom Fields takes away the pain of having to manually copy and paste your information into websites. For example, if you have a website like this one from the Bank of Melbourne, it requires a Card/Access Number field, Security Number and Password. Corresponding the website field title and the Custom Field Name will allow Keeper to auto-fill these fields with their values. Custom Fields may also allow the user to use the same record for multiple websites. For example, if a user has the same login and password for Amazon.com and eBay.com, the user may add the website address in the Custom Field Value and that single record will now recognize two different website logins. This allows the user to not have to create a record for each website where that username and password are used.
File Attachments - File attachments can be any type of file, photo, video or other document. An unlimited number of files can be attached to any Keeper vault record. File storage is an add-on subscription. If file storage is disabled, please contact your Keeper administrator or email sales@keepersecurity.com.
Two-Factor Codes - Keeper can protect and generate 2FA codes for any website or service that supports the use of TOTP (Time-Based One-Time-Passwords).
Notes - Any free-form notes can be protected in this field such as access instructions or confidential documentation.
Keeper records can be shared on an individual basis to other Keeper users. Keeper sharing technology uses secure RSA encryption to exchange the individual record keys. Therefore, in order to share or transfer a record to another user, the recipient must first have a Keeper account. Attempting to share to a user without a Keeper account will invite them to the platform. For more detailed information, visit Keeper's Security Architecture. To share a Keeper record with another user, while viewing the record, select Options > Share and then enter the email address of the recipient (or select from previously shared users). Edit and re-share permission can be applied to any shared records. Role enforcement policies can be applied from the Keeper Admin Console to control the ability for records to be shared. Only the owner of a record is able to delete a record. A non-owner may see a Delete button but this will only remove the record from the non-owner's vault. When the owner of a record deletes it from their vault, it will delete it from everyone's vault.
Record ownership can be transferred to another Keeper user. To perform a transfer, while viewing a record, select Options > Share and enter the email address of the recipient (or select from previously shared users). Select Transfer Ownership from the sharing permission dropdown menu. Note that after transferring record ownership, the record will no longer be accessible from your vault.
Through the use of Keeper Commander, records can be pushed to users in bulk.
Example usage of the "enterprise-push" command:
enterprise-push --team "Engineering Admins" push.json
enterprise-push --email user@company.com push.json
The "push.json" file is structured an an array of password object, for example:
[{"title": "Google","login": "${user_email}","password": "${generate_password}","login_url": "https://google.com","notes": "","custom_fields": {"Name 1": "Value 1","Name 2": "Value 2"}},{"title": "Admin Tool","login": "${user_email}","password": "","login_url": "https://192.168.1.1","notes": "","custom_fields": {}}]
Supported template parameters:
${user_email} User email address${generate_password} Generate random password${user_name} User full name
For more information about Keeper Commander please see our Github Page.
Every record created by a user is automatically backed-up through the Keeper Cloud Security Vault architecture. Every record change is also backed-up and a record version is created upon each change event. Each record is identified by a record UID and each record can have an unlimited number of version identifiers. Version History is a critical capability to ensure that a password or record change is never lost by accident. Version History also ensures that a deleted record can be recovered. When a record is deleted by the record owner, the record is moved into the Deleted Records trash bin. Records will remain in this location until the record owner explicitly empties the trash bin. Users can view the Version History of any Keeper record through Keeper Web Vault or Keeper Desktop App. To view a record's history, select a record, then select Options and Record History.
Keeper Web Vault and Keeper Desktop App include an Export capability which can be enabled by the Keeper Administrator. Exporting records from your vault can serve as a backup mechanism, however this does not retain any information about sharing relationships, folder structure or file attachments. If Export is allowed by the Keeper Administrator, we recommend that the customer stores the exported files in a secure location on an encrypted file system. The security and encryption model of Keeper purposely does not permit a Keeper Administrator to export user vaults. A user must be authorized on a Keeper record via the Team or User sharing capability in order to access and export vault information.
Keeper Commander has the additional capability of exporting data to an encrypted Keepass file, which retains file attachments.
Offline Mode allows users to have access to their vault from a web browser when they are not able to connect online to Keeper or to their SSO (if they have one). Note that “thick clients” such as desktop and mobile phones already have this capability, but it has been extended to users operating from web browsers.
Offline Mode is made possible by making a copy of your online vault to your local device. A user's vault data is stored in an encrypted format which is only accessible by providing their Master Password. Note, multiple users can share a single device (e.g. a laptop PC) and all users are able have their vault stored safely on that PC when offline.
A user’s devices (e.g. laptops that might not have offline access) will need to be “primed” with a cache of their vault by logging in with an online connection at least once. A mirror copy of their vault will be replicated to that device once completed.
User’s will know if their vault is available when offline via a lightning bolt icon indicating it has been loaded on that device when they attempt to access their vault offline. If the icon is not present, then that device will need to be setup using the steps described above. The X next to the user's email address allows a user to delete the local copy of their vault from the device.
Once logged in, a user will know if they are offline by an Offline Mode text indicator at that bottom of their vault screen.
Not all vault features are available online and record's will be "read only". For instance users can't create any new vault content such as record or folders when offline. When such a limitation occurs then a notice will be displayed.
SSO Account
If your organization's SSO is not available (e.g. is offline), then click on Login with Master Password to gain access to your vault offline.
A user's Master Password has to be setup by the user via the Settings menu for this offline access to be available.
See the Role, RBAC and Permissions, Account Settings page for instructions on how to restrict Offline Access.
