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, it doesn’t 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 only visible to you. If someone else changes the value, it will not affect you. You cannot see the value of other users, even as a workspace admin.

​
CLI

Use the --ispersonal flag when updating a secret: 
ek update DATABASE_URL --ispersonal
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.