Skip to main content
Personal overrides let individual team members set their own value for a secret in a specific environment. The override replaces the shared value only for that user and does not affect other team members or syncs.

​
Use case

During local development, you may need credentials that differ from the shared team values. For example:
  • A personal database running on your machine
  • An API key for your own sandbox account
  • A webhook URL pointing to your local tunnel
Instead of editing the shared value (which would affect everyone), you create a personal override.

​
How it works

When a personal override exists for a secret in an environment:
  • Dashboard: you see both values
  • CLI: ek run injects your personal value into the process
  • Syncs: syncs always use the shared value, not personal overrides
Personal overrides are stored as separate encrypted values, tied to your user account.

​
Creating a personal override

To enable personal overrides, a workspace admin needs to enable them in the project settings. See Environments for details.

​
Dashboard

In the project secrets table, click on a secret value and enter a value in the second input field of that environment. This input field is visible only to you. You cannot see other users’ values, even as a workspace admin, and changes they make do not affect your override.

​
CLI

The ek secret commands are deprecated and may be removed in a future release. Set personal overrides from the dashboard instead.
Use the --ispersonal flag when updating a secret:
This sets a personal override for DATABASE_URL in the currently configured environment.

​
Removing a personal override

Delete your personal override from the dashboard to revert to the shared value for that secret.