If your tenant does not include Secrets, the Secrets entry stays in the navigation for people who can read secrets. The page still lists the secrets you already hold and lets you rotate, disable, delete, destroy old versions and unbind them. Creating, generating, requesting, binding, adding destinations and granting access are unavailable, and the buttons for them are greyed out.
The Secrets page
The page header reads “Named values apps and agents use by handle. A secret is write-only: once stored, no screen can show it again.” Three buttons sit above the list:
A button you cannot use is greyed out with the reason beside it, for example that your role does not allow creating secrets.
With nothing stored, the page says No secrets yet and offers four ways to start: Set a value, Generate a value, Request from someone, and From your agent, where your AI agent makes a request with
dip secret request and hands you the link.
Once you have secrets, the list shows:
Filter by name, custody or status above the table. A line under the usage meter reads, for example, “6 of 200 secrets”. When some secrets exist that you cannot see, the page says “Some secrets are not shown because you cannot see them.”
Open requests appears above the list while any request is waiting. It shows each secret, what it is used by, the recipient, who asked and when it expires. Copy link works only in the browser tab that made the request, because the link is shown once and never stored; otherwise the row says the link was shown once and to revoke and re-request. Revoke closes the request. You can revoke requests you made, or any request if your role may delete secrets. The number of open requests also appears as a badge on Secrets while Settings is open.
Store a value
In New secret, enter a Name (the dialog shows the handle,secret:// plus the name), a Kind, an optional Description, and the value, typed or uploaded from a file. Choose Store secret. The value is encrypted when it arrives. The limit is 64 KiB.
Generate a value
In Generate a secret, enter the name, kind and description and choose Generate. The dialog then shows the value once, under the heading Copy it now. Choose I’ve copied it when you have. If you lose it, rotate the secret.A secret’s page
Open a secret to see its name, status, custody and kind, and the actions Bind to consumer, Rotate, Disable (or Enable) and Delete. A strip under the title reads Write-only · never shown, with the size limit and the current version. While the secret is awaiting a value it reads No value yet and says who it is waiting for and when the link expires. Four tabs:
Version lineage lists each version with its state (CURRENT, PREVIOUS, RETIRED, DESTROYED), how it was created and when. It adds “The previous version is kept for overlap while consumers move. Versions only move forward; there is no rollback.” A person with the
manage privilege sees Destroy beside a retired version.
Rotate
Choose Rotate, enter the new value and confirm. It becomes the next version. If someone else rotated first, the rotation is refused rather than overwriting theirs.Disable, enable and delete
Disable stops delivery by handle until you Enable it again; nothing is deleted. Delete removes the secret from lists and stops it being used. Its encrypted values are kept for the 30-day retention window unless a legal hold applies, as described in Secrets overview.Bind a secret to an app
Choose Bind to consumer (or Bind a secret on an app’s tab), pick the secret and the app, enter an Environment variable such asSTRIPE_KEY, and choose Bind. You need the use privilege on the secret. The binding is recorded; the value is not delivered to the running app yet.
An app’s Secrets tab
Each app’s page has a Secrets tab, “Secrets this app reads by handle. The app never receives a value in its manifest.” The table has Secret (name and handle), Delivery (Built-in), Route or handle (env plus the variable name), Status, Last delivery and Unbind. An app with nothing bound says This app uses no secrets.