Settings
Keys this site needs, set from here instead of from a terminal.
This page is for administrators. If you are signed in and seeing this, your account is not one — ask an admin on the people page. If you are not signed in, sign in first.
A secret is never shown back. For a masked field this page can tell you that a value is set, when, and by whom — never what it is. A screen that can show a key back is a screen that leaks every key to anyone who reaches it once.
Plain fields are the ones that are public by nature — an address you could read on the people page anyway, a Google client id that appears in every visitor's OAuth redirect. Those show their current value so you can edit rather than retype. Masking them would teach you that the asterisks elsewhere mean nothing.
Stored values are encrypted with this instance's SETTINGS_KEY
and win over anything set at deploy time. Clearing one falls back to the
deploy-time value if there is one.
| Key | What it does | State |
|---|
⚠️ SESSION_SECRET and ROOT_ADMIN
are not here and cannot be. The first verifies the session of the admin who
would be changing it; the second has to work when this database is empty,
which is exactly when it cannot be the place it is kept. Both stay
wrangler secret put.