Before you start
A Guardian Team, the group of devices that together approve each proposal, formed and usable. See Form your Guardian Team.
- A threshold vault in your organization, backed by that Guardian Team, with the Use access level on the folder you store into.
- The Edit access level on an item, to change or delete it.
- A seat that includes secrets. Basic and Guardian seats both include them.
This guide stores a password and its one-time codes in a vault, then uses, changes and deletes them in the Web App. It also imports the items of another password manager. Your Guardian Team, the group of devices that together approve each proposal, approves each of these actions.
Create a password
In the Web App
- Open the Web App (opens the SplitSecure web app).
- Go to Vaults → your vault, then open the folder for the password.
- Click New resource.
- Under What are you creating?, click Password.
| Field | Value |
|---|---|
| Name | The name members search for, such as GitHubRequired. It can’t be changed later. |
| Description (optional) | What the login is for |
| Websites | The sign-in address, such as https://github.com Click Add website for each other address. Leave it empty for a login with no website. |
| Fill on | Any page on this domainOr Only this exact host, or Never fill here. One per website. |
| Username | The account’s username |
| Password | The account’s passwordRequired. Strength rates it from Weak to Strong. |
| Custom fields | A Label and a Value for eachClick Add field. Check Hidden to encrypt the value with the password. |
Click Continue.
- On Review, check the details and the What voters will see box.
- Enter a Reason for creation (optional).
- Click Propose creation.
The request page opens and waits for the votes.
On each member’s device, the proposal appears under Requests. The member opens it, checks the details, then taps Approve. The proposal passes when the approvals reach the Guardian Team’s threshold.
The password appears in the folder, with its username and website under its name.
Add one-time codes to a password
Do this when a website turns on two-step sign-in and shows a QR code.
- Go to Vaults → your vault → the password.
- Click Add one-time codes. The button shows only when the password has no codes yet.
- Click Upload the QR code and choose a screenshot of the QR code. You can also paste the screenshot on the page.
- Check that Setup key or otpauth link is filled. If the website shows a setup key instead of a QR code, paste the key there.
- Check Name. It is the password’s name followed by “codes”.
The Websites and the Username come from the password, so the codes join its account.
Click Propose creation. The Guardian Team votes on their devices, as in Vote on the creation above.
The codes appear in the same folder, and the password shows them under Same account. Enter a first code on the website to finish its two-step setup: see Get one-time codes below.
For codes with no password in the vault, click New resource → One-time codes instead.
Reveal a password
In the Web App
- Go to Vaults → your vault → the password.
- Click Propose release.
- Enter a Reason for access (optional).
- Click Propose release.
The Guardian Team votes on their devices.
When the votes reach the threshold, the request page shows Revealed secret.
- Click the eye icon to see the password, or click Copy to copy it.
- Leave the page when you are done.
The browser can read the result once. After you leave the page, the request shows “This result isn’t viewable here”. Click Request again for a new approval.
Get one-time codes
In the Web App
- Go to Vaults → your vault → the one-time codes.
- Click Request codes.
- Under Codes for, choose 3 minutes, 15 minutes or 1 hour.
- Click Request codes.
The Guardian Team votes on their devices.
The request page shows the current code and the next one. The browser receives the codes for the period you chose, counted from the last vote.
The browser can read the codes once. Keep the page open while you need them. After you leave it, the request shows “This result isn’t viewable here”. Click Request again for a new approval.
- Click Copy code.
- Paste the code on the website before Expires in reaches 0.
When the codes run out, the page shows “These codes have expired.” Click Get new codes for a new approval.
Change a password
In the Web App
- Go to Vaults → your vault → the password.
- Click Edit.
- To change the password, type the new one. To keep it, leave Password empty. It shows Unchanged.
- Change the websites, the username or the visible custom fields as needed. Hidden custom fields keep their values.
- Click Propose update.
The Guardian Team votes on their devices. Under Hidden fields, the request lists each encrypted field it changes. Every other encrypted field keeps its value, and nobody sees it. The name can’t change.
For one-time codes, Edit changes only the Websites and the Username. To use a new setup key, delete the codes and add them again.
Delete an item
In the Web App
- Go to Vaults → your vault → the item.
- Click the More actions button (the three dots), then Delete.
- Enter a Reason for deletion (optional).
- Click Propose deletion.
When the Guardian Team approves, the vault destroys the item. Nobody can recover it.
Import from another password manager
In your password manager
The import reads an export file in your browser. The file never leaves your computer: only the encrypted items go to the vault. SplitSecure reads these exports:
| Password manager | Export file |
|---|---|
| 1Password | .1pux |
| Bitwarden | .json, without a password |
| Keeper | .json |
| Passwords app | .csv from Apple’s Passwords app, with the Title, URL, Username and Password columns |
Export your items from the password manager as an unencrypted file of the type above. See your password manager’s help for the steps.
The export holds every password in plain text. Delete it, and empty the trash, as soon as the import finishes.
In the Web App
- Go to Vaults → your vault, then open the folder for the items.
- Click Import.
- Click Choose file and choose the export.
The page lists the items to import and the number of requests the import sends. Under Not imported, it lists each item it skips, with the reason.
Click Import. Each request holds up to 500 records, and a login with one-time codes counts as two. A large export sends several requests.
The Guardian Team votes on each request on their devices.
The items appear in the folder. A login with a setup key arrives as a password and its one-time codes, in the same account. 1Password’s servers, databases, email accounts and API credentials arrive as Account items, and notes as Secure note items.
The import doesn’t check for items the vault already has. Passkeys can’t be imported: create them again from each website with the browser extension.
Troubleshooting
| Issue | Solution |
|---|---|
| Import is greyed out: “Import needs a vault with one team.” | The vault belongs to more than one Guardian TeamImport into a vault that one Guardian Team backs |
| “This export is encrypted. Export it again without a password.” | The Bitwarden export has a passwordExport again and choose the unencrypted JSON format |
| “This file isn’t an export from 1Password, Bitwarden, Keeper or the Passwords app.” | The file comes from another toolExport from one of the four password managers above |
| Add one-time codes is missing | The password already has codes in its accountOpen the codes from Same account |
| “Your seat doesn’t include creating secrets. Ask an admin to upgrade it.” | Your seat doesn’t allow itAsk an administrator to change your seat |
| The request waits | The votes haven’t reached the threshold yetAsk the members of the vault’s Guardian Team to vote on their devices |