Store a secret
For a beta user: store a credential under a name in the console, see the stored names, replace one with a new value, and remove one.
For a beta user whose connector needs a key. After this page you can store a credential under a name, see the stored names, replace one and remove one. Not here: how a connector gets its key (Connect an outside service).
Secrets is family 17, which reads four bars evidenced in the census at revision 3ec0e4f4, 2026-10-20. Three of those bars read under the older census rule, not the newer one: reachable, measured and natural-language. The census console bar has no reading key.
As of 2026-10-21, this page gives the console path only. The cloud SDK and command line name no method for this family's secrets. The cloud SDK is also built from source until its first publish.
Open the tab
Security in the left rail opens a page titled "Where a run meets its policy." Its Secrets tab lists the secret names your workspace stores.
Store one
While storing is turned on for your workspace, the Secrets tab shows a Store a credential button. It opens a form with a Name and a Value. Press Store to save.
A name is 1 to 255 characters of letters, digits, underscore, dot and hyphen. A value is up to 65,536 bytes. The form says "Typed once and never shown again: nothing here can display, copy or verify a stored value."
The list can lag a write by up to five minutes on some stores. The console merges into it the writes that one gateway instance took in the last five minutes for your workspace; that record is empty after a restart.
If the tab says "Adding or changing a secret isn't turned on for this workspace yet.", it shows no Store a credential button, no Rotate and no Remove, and the names still list.
See the names
Each row in the list shows a name with "added" and its date, and "rotated" and its date once the name has been rotated. With more than one name, a box labelled "Filter secret names" (placeholder "Filter names") narrows the names already read. With none, the tab says "No secrets are stored in this workspace."
Choose a name to open its drawer. The drawer shows Added, Rotated after a rotation, and Value, whose row reads "The value is never shown — not here, and not to a model." It also lists the connectors that name it under "Named by", from the first page of your connectors, and says how many it checked when it did not read them all.
Replace one
While storing is turned on, each name has an icon button labelled "Rotate" followed by the name. It opens the same form with the name filled in. Type the new value and press Store. Storing under a name that already exists rotates it and keeps the date it was first added.
Remove one
While storing is turned on, each name has an icon button labelled "Remove" followed by the name and "from the store". It asks whether to remove that name and says "The value cannot be read back, so it cannot be restored from here." Choose Confirm to remove it, or Cancel. The console then says that the name was removed from the store, or that it was not in this workspace's store, so nothing was removed.
With some secret stores, storing under a name you have just removed may be refused for a while. How long is not measured.
Who can change them
Storing, replacing and removing are for an owner or an admin where your org has them. Where the runtime serves a refusal for your role, the three controls can show greyed with its reason. If the list cannot be read, they stay pressable and the refusal arrives on the press.
Use the name
A connector names a secret by its name. Store the secret first, then register the connection (Connect an outside service).
What it does not do yet
Dated gaps, as of 2026-10-21. None is a step on this page.
- Reading a value back. The runtime's list, store and remove handlers for secrets return names, dates and acknowledgements, not values. The console has no control that shows a stored value.
- Driven live. Everything on this page is read from the console source and the cloud code at the cited revisions. None of it was driven against a deployed console for this page.
What it refuses
The census tenancy check for this family reads PASS on a receipt dated 2026-09-28 at cloud revision 811884ed: 7 of 7 isolation arms and 11 of 11 controls, with one principal in two tenants. The receipt does not measure the read-side deny in the secret store's access policy. A name outside the rule above is refused, and the form shows the reason. If the secret store cannot be used, the change is refused with the store's reason. A deployment without the secret store says "Secrets aren't on this deployment."