Activity3 1Password Field Guide Activity3 Support Center Support Center Our offices 24/7 Helpdesk (818) 668-3903
Getting set up · 3 of 4

How vaults work

Private vs. shared vaults, who can see what, and how to decide where an item belongs.

A vault is a container with its own guest list

A vault is a group of items, and access is granted per vault, not per item. If someone can open a vault, they can see every item in it. If they can't, they don't know it exists. That single rule explains everything else about how vaults should be organised.

Vaults are also the unit of sharing. You don't "share a vault item" with a teammate by adding them to the item — you put the item in a vault they already have access to. (The exception is the one-off share link in Sharing a single password safely.)

The vaults you'll see

VaultWho can see itWhat belongs in it
Private (sometimes shown as "Personal" or "Employee") Only you. Administrators cannot read its contents — not the helpdesk, not your manager, not Activity3. Logins that are genuinely yours alone: your own HR portal login, your personal 2FA codes, your own accounts if your company allows personal use.
Shared / team vaults (e.g. Finance, IT Admin, Marketing) Everyone granted access to that vault, typically a team or department. Anything the business owns: vendor portals, shared service accounts, social accounts, licence keys, the accounts that must survive someone's holiday or resignation.
Project or client vaults The people on that project or account. Credentials scoped to one client or engagement, so access ends cleanly when the work does.
The test that settles nearly every case

Ask: "If I were hit by a bus tomorrow, would the business need this?" If yes, it belongs in a shared vault. Your private vault should hold nothing the company would have to break into an account to recover.

Why "it's in my private vault" is a problem

Work logins that live only in one person's private vault create real, recurring costs:

Moving work logins out of your private vault walks through fixing this.

Why "just put everything in the shared vault" is also a problem

The opposite mistake is one giant vault everyone can open. That means the summer intern can read the domain registrar login and the payroll account. Vaults should be scoped so that access matches the job — a few well-named vaults per team beat one vault for everything.

Your personal items shouldn't go into a shared vault either. If you move your own bank login into Finance, an entire department can now see it. Personal stays private; business goes shared.

Deciding where an item goes

  1. Who owns the account? If the company does — it was set up with a company email, paid on a company card, or used for company work — it goes in a shared vault.
  2. Who else needs it, ever? If the answer is anyone other than you, shared vault. "Needs it in an emergency" counts.
  3. Which team's job is it? Pick the vault named after that function. If none fits, ask the helpdesk to create one rather than dropping it into the nearest vault.
  4. Everything else goes in your private vault.

Working with vaults day to day

Ask before you create vaults

Most people can't create vaults, and that's deliberate — sprawl is the enemy of knowing who has access to what. If you need a new one, ask your 1Password administrator or the Activity3 helpdesk, and say who should have access and what the vault is for.

Stuck, or something looks different?

1Password's apps change their wording from time to time, and your company may have vaults set up differently from the examples here. If a step doesn't match what you see, don't guess and don't work around it — call the Activity3 helpdesk at +1 (208) 944-9200 or email info@activity3.com and we'll walk through it with you.