Vault

Share the access the work needs.

Give credentials a clear home and make access an explicit choice. Cedros Vault keeps secrets organized in collections, with controls for personal, team, and assistant use, so the people and tools doing the work can use the access they need.

Explore plans /pricing See the platform /about

Cedros Vault listing example credential metadata and team or assistant access scopes without revealing values. /media/objects/9a4c293de52c5e9b0ad52744c10a01d94ccb5b4ecc04a5ec618315f30dc56742/retained/8f82e0cb-6db8-5603-b323-43800732959a/assets/2026/09/88fe6ae2-56cc-4ad8-8304-1bb4bff9ffde.webp Real Cedros interface · example workspace data

Keep the credential and its access together

Keep credentials easy to identify

Save a credential with a useful name, collection, and description of its purpose. Keep the secret value separate from the ordinary details that help your team find it. Organize access around the service or work it supports instead of scattering credentials through messages.

Choose personal or shared access

Personal credentials stay private to their owner. For shared items, control whether team members with Vault access can read the credential; administrators retain access to shared items. These choices make the scope visible when you create or maintain an entry.

Grant access to selected assistants

Enable assistant access on an eligible shared credential and choose which assistants are allowed to read it. Supported task and routine workflows can then use that access. Personal items remain unavailable to assistants, and storing a secret alone does not grant assistant access.

Update a secret with its history available

Change the credential value independently of its descriptive details and access settings. Review earlier versions and recover an available value when needed. Recovering a stored version updates Vault; it does not reactivate a credential that the external provider has already revoked.

Connect credentials to the services that need them

Use Vault-backed secret references where Cedros supports them for provider setup and assistant workflows. Keep the credential in the dedicated secret workflow while ordinary settings identify which service to use. This gives ongoing access a place to maintain as providers and tasks change.

Keep access current as responsibilities change

Review shared and assistant access when a teammate, integration, or task no longer needs a credential. Rotate credentials with their provider when required and update the stored value. Include the deployed Vault’s recovery requirements in the site’s backup planning.

Useful to know

Can the assistant read my personal credentials?

No. Personal items remain private. Assistant use requires an eligible shared item with assistant access enabled and an allowed assistant identity.

Who can read a shared credential?

Administrators can read shared items. Team access lets team members with Vault permission read the credential, and assistant access is controlled separately.

Can I recover a previous value?

Available earlier values can be recovered through version history. Restoring the stored value does not change the external provider’s credential status; a revoked key still needs replacement at the provider.

Keep useful access organized and intentional.

Manage credentials alongside the team, services, and assistant workflows that use them.

Talk about your website /contact