Unbedocs

Dashboard

Use the dashboard to organize secrets, control access, issue machine credentials, and understand every change.

Resource model

Workspaces

Team boundary for projects, members, tokens, billing, and audit events.

Projects

A single app, service, or worker with its own access boundary.

Environments

Independent values for development, staging, production, or another release lane.

Secrets

Encrypted key-value pairs with previews, versions, and rollback history.

Manage secrets

Open a project and select an environment before creating or editing a secret. Keys should use the exact environment variable name expected by the application. Values are concealed by default; reveal them only when you need to verify or copy the complete value.

Production changes

Confirm the selected workspace, project, and environment before saving. The same key can intentionally have a different value in every environment.

Version history

Every update creates a version. Use history to see when a value changed and roll back to an earlier version when a rotation or deployment causes a regression. A rollback creates a new current version; it does not delete the intervening history.

Members and roles

Invite people at the workspace level and assign the narrowest role that lets them do their job. Review membership when ownership changes or a teammate leaves the organization.

Tokens and audit log

Create scoped tokens for CI, deployment systems, agents, and other non-interactive clients. The audit log records secret access and changes, rollbacks, token activity, and project events so the team can trace what happened without exposing stored values.

On this page