Skip to main content

Keep access organized with the team

The right details, for the right people.

Organize team logins, API keys, and secure notes in credential vaults. Choose whether a vault belongs to the whole workspace or a selected group of members.

Illustrative record

Made for the work

A little more detail.
A lot more possibility.

01

A shared home for credentials

Store login details, API keys, notes, and custom fields together, with names and tags that make items easier to find.

02

Share by vault

Make a vault available to the workspace or restrict it to selected full-seat members with viewer, editor, or manager access.

03

Reveal only when needed

Open an item's secret values deliberately rather than leaving them exposed in the list.

04

Keep an access trail

Review vault activity, including logged reveals, so credential access has a visible history.

From idea to everyday

Put it to work.

A practical starting point for shared credentials.

  1. 01

    Create a vault

    Add the Credentials page and choose who should be able to access the vault.

  2. 02

    Organize the essentials

    Add logins, keys, and notes with clear names, useful tags, and the fields your team needs.

  3. 03

    Manage access over time

    Update member roles and review activity as people and responsibilities change.

A little more clarity

Good questions.

How are credential secrets protected?

Secret values are encrypted at rest with a key Scribed holds, and access is logged. This is server-side encryption, not a zero-knowledge password manager.

Can workspace administrators read every vault?

Administrators can manage vault metadata and access grants, but reading a vault's secrets requires an effective vault role. Restricted vaults give access through explicit grants.

Keep exploring