Keeper looks like "just a password manager" from the outside, but it's really one encrypted vault with several ways in, plus company-wide management on top for our MSP customers.
The building blocks
Vault — the encrypted container for everything: logins, passkeys, secure notes, files, payment cards, identities.
Record — one saved item (e.g. one website login). Records have fields (login, password, URL, notes) and can hold custom fields like a Two-Factor Code.
Folder / Shared Folder — how records get organized, and how a group of records gets shared with a team while staying centrally controlled.
KeeperFill — the browser extension that watches web pages, offers to save new logins/passkeys, and autofills saved ones.
Custom record types
Beyond the built-in "Login" record, Keeper lets a business define its own record templates — say, a "Server Credential" type with fields for hostname, port, and SSH key, or a "Client Wi-Fi" type with SSID and passphrase.
Who can create one: only an admin whose role has the "Manage Record Types in Vault" permission turned on (Admin Console → Roles → a role → Administrative Permissions).
Who can use one once it's published: any user whose role has that record type enabled under Roles → Enforcement Policies → Record Types. It's enterprise-wide once published — not something an individual user turns on for themselves.
Sharing: a record made from a custom type shares exactly like a normal record — to a person directly, or by dropping it in a Shared Folder.
🖼️ Screenshot not uploaded yet — Creating a custom record type Admin Console → Roles → (a role) → Record Types, or the Web Vault's “Add record type” screen. Screenshot the type editor. A trainer can add it at /admin/screenshots.
Say this to a customer"If your business has something that doesn't fit a normal login — like a piece of equipment with a serial number and a PIN — we can build a custom record type for exactly that shape of information, and everyone on your team sees it the same way."
The Admin Console (what we use, not the customer)
For MSP customers, each company is a Managed Company with its own node tree (like folders, but for organizing users and policy) and roles (which set password policy, 2FA requirements, and which record types are available). This is where Simple Technologies sets up a new customer, not something the end user ever needs to see.
🖼️ Screenshot not uploaded yet — Admin Console node/role tree Screenshot the node/role tree for a Managed Company so trainees recognize the shape of an account. A trainer can add it at /admin/screenshots.
Why this matters for the paid visit
A customer never needs to understand node trees or role policy — that's on us. What they DO need from the technician is confidence that:
Their password is now long, random, and unique.
Keeper will fill it for them — they don't need to remember it.
Two-factor is on wherever the site supports it.
Any device or passkey they don't recognize has been removed.
That checklist is the Security Tune-Up — see the next guide.
Simple Technologies · Login Lab — a training sandbox. Nothing here is a real account. · Guides · Training Track