Give each department its own vault, and keep one company-wide vault for the handful of things everyone genuinely needs. In SecureGate Card, a member sees their own department's vaults and the company-wide ones, and nothing else. Finance doesn't see marketing's social accounts. Marketing doesn't see the bank.
It's the same rule as the office keys. Everyone gets the front door. Only finance gets the filing cabinet with the cheque book in it. The work is deciding which is which, and that takes an afternoon, not a project.
Why one vault for everyone goes wrong
Most small companies start with one shared vault, or one shared spreadsheet, because it's quick. It stays fine until one of three things happens.
- Someone leaves. Every password they could see now has to be changed, which with one vault means all of them. In practice nobody changes all of them.
- Someone's account is taken over. The attacker gets whatever that person could see. With one vault, that's the bank, payroll and the domain registrar, through the login of a part-time marketing assistant.
- Someone asks who changed what. With forty people writing to one vault, the audit log is noise.
Splitting by department doesn't stop any of these. It makes each one smaller: fewer passwords to change, less for an attacker to take, fewer names in the log.
How it works in SecureGate Card
Departments and shared vaults come with both paid plans, Team and Business. The pieces are:
- Departments. Finance, Operations, Sales, whatever matches how you work.
- Vaults. Each shared vault belongs either to the whole company or to one department.
- Members. People join by email invitation and sit in a department.
- Roles. Permissions are granular: reading or writing vaults, managing members, departments, roles and vaults, setting policies, branding, billing, reading the audit log.
- Audit log. On Business, the organisation's record of who did what.
The visibility rule is simple on purpose: your department's vaults, plus the company-wide ones. A role decides what you can do in the vaults you see.
Three roles are usually enough
- Member. Reads the vaults they can see. Most people.
- Editor. Reads and writes vaults. One or two per department, usually the team lead.
- Administrator. Manages members, departments, roles and vaults, and sets policies. The owner and one deputy.
Billing and branding are separate permissions. Give billing to whoever pays the invoices, who may not be an administrator at all. And on Business, give audit log access to at least one person who can't change anything, so someone checks the people who can.
A split that works for 25 people
Here's a starting point for a typical 25-person company. Change the names; keep the shape.
| Vault | Who sees it | What goes in it |
|---|---|---|
| Company-wide | Everyone | Guest Wi-Fi, printer portal, shared video-call account, the visitor sign-in tablet |
| Finance | Finance team (3 people) | Online banking, payroll, HMRC, card processor, supplier portals |
| Sales | Sales team (6) | CRM, quoting tool, LinkedIn Sales Navigator |
| Marketing | Marketing (3) | Social accounts, website admin, newsletter tool |
| Operations | Operations (10) | Courier accounts, warehouse system, supplier ordering |
| IT and admin | Office manager and IT provider (3) | Domain registrar, Microsoft 365 or Google admin, router |
Three vaults people argue about, and where they belong:
- The domain registrar. Not company-wide. Whoever controls the domain controls your email, and whoever controls your email can reset everything else.
- Payroll. Finance, even if HR runs it day to day. Salaries are the one thing people will go looking for.
- The guest Wi-Fi. Company-wide is fine. It's a guest network. If it isn't, that's a different problem.
Setting it up in an afternoon
You can start small. Set up Finance first, because that's where the risk sits, and move the other teams over one at a time.
- List every shared login. Not the personal ones: the ones more than one person uses.
- Mark each one with the department that owns it. If two departments use it, pick the one that would be blamed if it leaked.
- Create the departments and their vaults.
- Put the things everyone needs in the company-wide vault. Keep it short.
- Create two or three roles: people who read, people who edit, people who run the organisation.
- Invite people by email into the right department.
- Write down who owns each department's vault, so there's a name to ask when something's wrong.
- Change the passwords that lived in the old shared spreadsheet. Everyone who ever opened it still knows them.
People who work across two teams
This is the awkward case, and it's better to decide it before you set up than after. A member sees their department's vaults and the company-wide ones. If your office manager also does the books, place them where the riskier credentials are, usually finance, and move only what they truly share with operations into the company-wide vault.
The other option, widening the company-wide vault until it covers everybody's job, is how you end up back at one vault.
If that happens a lot in your company, your departments are probably too narrow. Merge them.
Leavers and the audit log
There's no SCIM or single sign-on today, so nobody leaves automatically. When someone goes, an administrator removes them from the organisation in the panel. Put it on the leaver checklist next to the laptop and the door card.
Then change what they could see. With department vaults that's their department's vault and the company-wide one, not every password the company owns. That's the practical payoff of splitting.
On Business, the audit log records what happens in the organisation. Smaller vaults make it readable: when something changes in the finance vault, the list of people who could have done it is three names, not twenty-five.
Common mistakes
- A department per person. Twenty-five departments is twenty-five vaults to maintain. Group by what people share, not by job title.
- A company-wide vault that grows. Every "just put it in the shared one" widens it. Review it every quarter.
- Admin rights for everyone in a hurry. The person who can manage roles can give any permission, including to themselves. Keep that to two people.
- Personal passwords in shared vaults. Someone's own email belongs in their personal vault, not in Sales.
Team or Business
Departments, shared vaults, roles and email invitations are all on Team, at €4 per user a month or €38 a year. For 25 people that's €100 a month, or €950 a year paid annually.
Business adds office-only network access, session and password policies, the audit log and white-label, at €8 per user a month or €77 a year. If the finance vault is the reason you're doing this, read about the network policy before you pick a plan. Both have a 14-day trial that doesn't ask for payment details until you subscribe. Pricing has the full table.
When it fits, and when it doesn't
It fits a company of five to fifty people with three or more teams that share logins inside the team and shouldn't share them outside it. That's most companies past about eight people. It fits better if your staff already carry access cards, because a card they already have can become one of the ways into the vault.
It doesn't fit if you need people added and removed automatically from Microsoft or Google: we don't have SSO or SCIM. It doesn't fit if you need fine-grained sharing where one person sits in several groups at once; Bitwarden's collections and groups and 1Password's vault permissions are more flexible. And it doesn't fit if the provider must not be able to read the vault: we encrypt with AES-256-GCM on our servers, with a key we hold.