Replace or delete a secret
When a token expires or is revoked, put the new one into the same secret: every task and project that uses it picks up the new value, and nothing else needs to change. When the connection is no longer needed, delete it.
Who can do this: replacing a value needs the permission to edit the secret; deleting needs the permission to delete it. Without them, Edit or Delete doesn't appear. Only its owner edits a personal secret, but an Org Owner or Admin can also delete one that belongs to a member of the organization.
Replace a secret

- In the sidebar, select Directory, then the Secrets tab.
- Select the secret's name, or Edit in its ⋯ menu. It opens on the Details tab.
- Find the secret field to replace. It shows dots (●●●●●●●●●●●), which clear when you select it.
- Type or paste the new value.
- Leave every other secret field empty to keep its stored value.
- Select Save.
Turning NodeVault on or off re-seals every value, so each secret field asks you to re-enter it before Save. See How NodeVault works.
If the tab says Read-only, you can't change this secret; it names who can.
Delete a secret

- On the Secrets tab, find the secret's row. Use Search if the list is long.
- Select ⋯ at the end of the row.
- Select Delete.
- Read the dialog: it names the secret.
- Select Delete to confirm, or Cancel to keep it.
Deleting removes the secret and every value stored with it, and it can't be undone. Tasks and projects that used it stop receiving it, and an environment variable read from it gets no value.
Related
- Store a new connection instead: Add a secret.
- Every field on the tab: Secrets.
- What happens to a stored value: How secrets work.