Credential Vault
AES-256 encrypted secrets, revealed only where you choose.
Encrypted at rest, gated by role
Every credential is stored with AES-256-GCM encryption. Reveal permission is a role, not a favour, technicians can see that a credential exists without ever seeing the secret itself, while the people you choose can reveal it when a job genuinely needs it.
Every reveal is logged, so there is always an answer to 'who looked at this, and when'. Passwords stop being something that floats around in chat messages and shared documents.
The end of passwords in spreadsheets
Most teams keep client passwords somewhere they should not: a spreadsheet, a notes app, a pinned message. Anyone with the file has everything, and there is no record of who opened it.
The Credential Vault replaces all of that with a single encrypted store where access is a permission you grant, not a file you email around.
Linked to the client and the asset
Credentials do not sit in a vacuum. Each one links to the client and the specific asset it belongs to, so when a technician opens a job the right logins are already attached.
That saves the daily back-and-forth of asking where a password lives, and it means a credential is never orphaned when someone leaves.
Import what you already have
Bring an existing KeePass vault across in one import, rather than re-entering every credential by hand. Your history comes with you, so moving to Atlas CS does not mean starting from an empty page.
Once imported, everything inherits the same role-based reveal rules and audit logging as anything you add later.