Skip to main content
Project secrets are shared across everyone working on a project - team credentials, service accounts, and project-specific configuration. They’re ideal for secrets the whole team needs but that shouldn’t be organization-wide. Project secrets have middle precedence. They override organization secrets but can be overridden by user secrets. This lets teams set project defaults while individuals can still customize.

​
Manage project secrets

Navigate to Project → Secrets.
Project secrets page showing list of shared secrets with type and name columns
From here you can create, edit, and delete secrets. Each secret can be an environment variable, file, or container registry credential.

​
When to use project secrets

  • Shared service accounts: Database credentials, API keys for project-specific services
  • Project configuration: Environment-specific settings the whole team needs
  • Container registry access: Private images for this project’s Dev Container
For personal credentials like your own Linear or GitHub token, use user secrets instead.