Nobody uses your organization’s passwords, passkeys and one-time codes without an approval from your Guardian Team, the group of devices that together approve each proposal. SplitSecure keeps the credentials in a vault, so a stolen laptop or a compromised account, an administrator’s included, can’t use them without that approval.
What SplitSecure guarantees for each credential
| Credential | What it is | What SplitSecure guarantees |
|---|---|---|
| Password | A login for one or more websites, with its username, websites and custom fields. | The password and the hidden custom fields are encrypted in the vault. They leave the vault only for an approved request, encrypted for the browser or device of the person who asked. |
| One-time codes | The setup key behind a website’s two-step sign-in, which makes its 6-digit or 8-digit codes. | Once you add or import the setup key, it never leaves the vault. Nobody can read it or export it, administrators included. After each approval, the vault computes only the codes for the period that the request asked for, and sends those codes. A request can ask for 1 hour at most. |
| Passkey | A passkey, a sign-in key pair that replaces a password on a website. | The vault creates the private key, and the key never leaves the vault. Nobody can export it, administrators included. Each use starts with an approval. |
How it works lists exactly what leaves the enclave for each use.
To move from another password manager, import its export in the Web App. Your browser reads the file, and the file never leaves your computer.
Every use needs an approval
Each action on a credential is a proposal: creating it, changing it, deleting it, and each use. A use is a reveal of a password, a request for codes, a sign-in with a passkey, or a fill in the browser.
The members of the vault’s Guardian Team vote on their devices, in the SplitSecure mobile app. The action runs only when the votes reach the Guardian Team’s threshold, the number of shares that must approve.
Approve once, then sign in for a while
One approval can cover several sign-ins. You choose how long a credential stays ready: 3 minutes, 15 minutes or 1 hour.
- In the browser extension, SplitSecure keeps what it filled ready in that tab. Another sign-in in the tab needs no new approval until the time runs out.
- On your device, Use on This Device keeps a login, its codes or a passkey on the device. The device’s AutoFill fills them in apps and websites until the time runs out. AutoFill fills nothing else.
When the time runs out, the credential leaves the browser tab or the device, and the next use needs a new approval.
Credentials of the same account
A website often has a password, one-time codes and a passkey for the same username. SplitSecure treats them as one account when they are in the same folder, with the same username and a website on the same domain. The Web App shows the password and its codes under Same account, and one approval fills both in Chrome. On your device, one approval keeps the whole account, its passkey included.
Who does what
| You want to | Read |
|---|---|
| Know what SplitSecure protects, and who can see what | How it works |
| Create, import, reveal, change or delete credentials | Store credentials in a vault |
| Fill and save passwords and codes in Chrome, and use passkeys | Use the browser extension |
| Sign in with AutoFill on an iPhone, iPad or Android device | Use credentials on your device |
Approvers vote in the mobile app, under Requests. Each request shows the item’s name, its username and its websites before the vote.
Before you continue
You need a threshold vault in your organization, a vault that a Guardian Team backs, and the SplitSecure mobile app on the devices of the Guardian Team’s members. The next guide stores a first password in that vault.