SalesFision Platform application
The access your organisation runs on, under one set of rules.
Vault is where the keys are kept: a password manager with shared vaults. Passwords and other credentials are stored safely and shown masked, copying is an action that gets recorded, and you decide per person and per team exactly who sees what — with a trail of who opened what.
Configure Vault Do the Business Scan
- Every account recorded once, under the organisation and the system it belongs to
- Access per person and per team — and three roles that keep reading, maintaining and removing apart
- Opening, copying, adding, changing and removing all land in a trail the application cannot rewrite
Access gets arranged in private, and nobody can prove who has what.
Every system that gets added brings a login with it, and each one is handed over in the quickest way available at that moment: a message, a note, a colleague who remembers. It works until someone leaves, until a system starts refusing, or until somebody asks you to show who can reach what.
- A login lives in a chat from two years ago and the one person who knows is away.
- Someone leaves on Friday and on Monday nobody knows which accounts to close.
- Three accounts exist for the same system and only one of them still works.
- A customer, an insurer or an auditor asks who can reach their data, and the answer takes a week.
What changes when access is written down once.
-
Access becomes a list you can walk through
Every account under the organisation it serves and the system it lives in. Onboarding, offboarding and a handover start from that list instead of from somebody’s memory.
-
Nobody gets in by accident
The application has to be switched on for the workspace, the workspace has to be in good standing, the person has to have been given access themselves, and that access carries one of three roles. A senior role elsewhere in the Platform grants nothing here.
-
The secret lives in the vault, not in a chat
Passwords and other credentials sit safely in shared vaults, shown masked. Copying is a recorded action, so the secret lives in one place instead of in messages and notes.
-
You can show what happened
Opened, added, changed — including which fields — and removed, on the entry itself. The application cannot rewrite that history, not for anyone.
What your team can do with Vault.
The vault itself
- Record every account under the organisation it serves and the system it lives in
- Give an entry a label, the username that belongs to it and the tags you sort by
- Keep the secret itself safely in the vault: shown masked, and copied with an action that gets recorded
- Write down what a colleague needs to know: who to call for a reset, which account this one replaced, where the recovery codes are held
Finding it back
- Search organisations, systems, labels, usernames and tags from every page in the application
- Get the results grouped as organisations, systems and accounts, so one click lands you on the right entry
- Filter a set of accounts by tag: live, staging, administration, the accounts that belong to a system rather than a person
- Open the login page of the system, or copy the value, from the entry itself
Who may, and who did
- Give access per person: without access granted here nobody enters, however senior their role elsewhere
- Keep three roles apart — read, maintain, and the one role that may remove something for good
- Keep every workspace fully separated, so one organisation’s vault is invisible from another
- Read back the recent activity on an entry: opened, added, changed with the fields that moved, and removed
Sharing and temporary access
- Share passwords through a shared vault, instead of through a message that sticks around
- Decide per vault who gets in and what sharing means: read only, copy too, or maintain
- Give temporary access that ends by itself — for a migration, an external specialist or a job with an end date
- Read back per vault who opened and copied what, so offboarding and a review have something to stand on
From scattered logins to one set of rules.
The same path for every account, whether it belongs to your own office, a brand you run, a supplier or a customer.
-
The organisations come in first
Your own company, the brands under it, the suppliers you depend on and the customers you work for — each one with the systems that are actually in use.
-
The accounts go underneath
A label that says which account it is, the username, and the tags you want to filter on later: live, staging, administration, or the accounts nobody personally owns.
-
The secret goes into the vault
The password, key or recovery codes are stored safely in the vault and shown masked. Copying is an action that gets recorded, just like opening.
-
Access is granted per person
Access with one of three roles: read, maintain, or maintain and remove. Without access the application stays closed, and a workspace that is suspended closes it for everyone.
-
Someone leaves, or you review
Open the organisation, walk its systems, close what has to go and hand over what stays. What was opened, changed and removed is on the entries, so the review has something to stand on.
What your team looks at.
One organisation: the accounts that belong to it, the vaults you share, the people who may reach them, and what happened to them.
Vault
- Password WordPress — administrator Copy
- API key Payment provider — live key Copy
- Service account Backup export — nightly Copy
- Recovery codes Mail account — backup codes Open
- Team login Invoicing software — team access Copy
Who can reach this organisation
- Ravi Read, maintain and remove Vault admin
- Sanne Read and maintain, never remove Vault editor
- Team Support Read and copy, for the migration Until 1 October
- Finance Only the administration vault Under review
- Colleague who left Every account closed or handed over Closed 30 August
Shared vaults
| Vault | Shared with | Rights | Ends | Status |
|---|---|---|---|---|
| Client environment migration | Team Support | Read and copy | Until 1 October | Temporary |
| Website — live | The development team | Read and maintain | No end date | In use |
| Hosting — supplier | External specialist | Read only | In three days | Ends soon |
| Administration | Finance | Read only | No end date | Shared |
| Praktijk Bloem — management | Ravi and Sanne | Read, maintain and remove | No end date | Managers |
Access and trail
Studio Noord · WordPress · administrator
- Today, 09:12 Entry opened Ravi Opening the entry is the event itself — there is no separate reveal that can be missed. Opened
- Today, 08:55 Temporary access granted to Team Support Ilse For the migration, and it ends by itself on 1 October. Until 1 October
- Yesterday, 16:40 Entry changed Sanne Fields: label, username. Changed
- 30 August Access closed for a colleague who left Nadia Walked through the systems under this organisation, one entry at a time. Offboarding
- 12 August Entry added Ravi Under Studio Noord, with the password safely in the vault. Added
Example data. Vault stores passwords and other credentials safely in shared vaults: masked values with a copy action that gets recorded, access per person and per team, temporary access that ends by itself, and a trail of who opened what.
Access follows the organisation.
Vault does not keep its own list of organisations or its own list of people. It uses the ones the rest of the Platform already maintains, and hands the access question back to the place where it comes up.
-
CRM to Vault
The organisations come from the record your team already keeps, so a system is never filed under a name nobody recognises and your own company sits in the same list as the ones you work for.
-
HR to Vault
Someone joins, moves to another team or leaves. HR knows the date; Vault holds the list of accounts that has to follow it, so offboarding is a walk through that list rather than a search.
-
Vault to Service Management
A request that needs an account does not need a password pasted into the thread. It needs the entry it belongs to, found in two words by someone who is allowed to see it.
-
Vault and Knowledge
How you name an account, what belongs in a note and what never does: written down once, so a new colleague does it right the first time. Included for every Platform user.
-
Vault to Customer Portal
When a customer wants to know who can reach their systems, that conversation belongs in their own environment rather than in email. Customer Portal is a product of its own with a fixed monthly price.
Price and licence
- Vault Start €9 per month Up to 10 users
- Vault Business €39 per month 11 to 50 users
- Vault Scale €99 per month 51 to 100 users
- Vault Enterprise on request More than 100 users
All prices excluding VAT; you pay per month. No platform surcharge.
What the licence covers, and what we agree with you separately:
Included
- The application, with the included users or capacity
- SalesFision Knowledge is included free with selected paid apps and bundles.
- Standard onboarding
- Regular support, maintenance and bug fixes
Separate proposal
- Additional consulting and training
- Complex integrations and custom work
- Migration of existing data
- Customer Portal (a product of its own)
Calculate your package See all pricing
Additional consulting, training, complex integrations and custom work are agreed with you up front, so you always know what you are buying.
What people ask before they start.
What does Vault do?
Vault is a password manager with shared vaults. It keeps the register of organisations, systems and accounts, stores passwords and other credentials safely, shows values masked and records every copy action. You give access per person and per team, with three roles and complete separation between workspaces; temporary access ends by itself. What was opened, added, changed and removed sits in the trail.
Does Vault hold the password itself?
Yes. Passwords and other credentials are stored safely in the vault, shown masked, and a copy action is recorded like any other event. That way the secret lives in one place, instead of in chats and notes.
Who can see what is in it?
Four things have to be true before anyone opens it: the application is switched on for the workspace, the workspace is in good standing, the person has been given access themselves, and that access carries a role. Read, maintain and remove are three separate roles, you share a vault per person or per team, and one workspace’s vault cannot be reached from another at all.
Does it show who opened an entry?
Yes. Opening the entry is the event, so a look is recorded even when nothing is clicked afterwards, and a change records which fields moved. Each entry shows its recent history, and the application will not let anyone rewrite it. We claim no more than that: someone with direct access to the database sits outside what an application can guarantee.
Can we use this for our own organisation, not just for customers?
Yes. An organisation here can be your own company, a brand you run, a supplier you depend on or a customer you work for. Your own organisation is marked as internal and sits at the top of the list, with its own systems underneath it.
Can we move an existing list of accounts into it?
That is usually the first piece of work. We go through what you have now — a sheet, a document, a few people’s memories — and land it as organisations, systems and accounts with the tags you want to filter on. Migration is separate work with a proposal of its own, apart from the licence.
What does Vault cost?
A fixed amount per month, with the package that fits your number of users; within a package there is no price per user. You will find all packages above under Price and licence and on the pricing page. Knowledge is included.
Can I pay per month?
Yes, you pay per month.
Start with Vault
Choose Vault for your team and see what it costs. Not sure where to start? The Business Scan gives you a recommendation.
Configure Vault Do the Business Scan
Moving an existing list of accounts, agreeing which part you need first, or setting the access rules against your own departments and suppliers? Plan a meeting and we will scope it.
