The Runtime stage for an example app. Saved values stay masked until
revealed by an authorized Admin.
Use **Form** to edit one value at a time. Stored values are masked until an authorized Admin reveals them with the eye icon; reveal a masked value before editing it. The **Editor** tab lets an Admin work with `KEY=value` lines for the selected stage. It accepts quoted values, comments, and multiline quoted strings. An unchanged value stays saved. Removing a declared key from the manifest removes its saved value on the next successful sync of that environment.
## Reuse a shared value
If several workloads need the same value, save it once under **Manage → Shared secrets** for the appropriate stage. Keep `API_TOKEN` declared in each workload manifest, then set its workload value to a reference:
```text title="App → Settings → Secrets → Runtime" theme={"system"}
API_TOKEN="{{globals.API_TOKEN}}"
```
The reference reads the workspace Runtime value for `API_TOKEN` when the workload runs. Shared values are **not** injected into workloads automatically. A reference can also appear within a larger value, such as `Bearer {{globals.API_TOKEN}}`. A missing reference stops deployment. Shared values are stage-specific but available across environments, including previews, so use distinct workspace keys when environments need different credentials.
Only an authorized Admin can reveal a saved value. Hovering over a visible `{{globals.KEY}}` expression can preview its referenced shared value; hovering over a variable name does not reveal a secret.
