Company connections
Admins manageShared by the whole workspace. Their keys are kept in Google Secret Manager and set by Steele — this page never sees one. Manage shows what each may do and how it was checked.
My connections
Only youYour own accounts, connected by signing in on each provider's own page — the workspace never sees a password. Connecting shares nothing with the rest of the company: admins can see that you connected, which permissions you allowed and when it last worked, never what is in the account.
People's connections
AdminsWho has connected which account, the permissions they allowed and when it last worked. Never the account itself, what is in it, or a token. Revoke disconnects it for them and, where the provider allows, withdraws the workspace's access there too.
Renew API keys
Owner and adminsProvider credentials are what other companies issue to Renew — the Monday, Medallion and Connecteam keys above, and each provider app's client secret. They live in Secret Manager and never appear here. Renew-issued keys are what Renew hands an outside integration so it can call Renew's own API: one per integration, each with its own permissions, expiry and revocation. A new key is shown once; only its fingerprint (a SHA-256 hash) is kept.
A key looks like rnw_<key id>_<secret>: the key id (16 characters) names it in lists and logs; the secret (43 characters) is what proves it. Send it only from a server, in the Authorization header — never in an address, a browser page or a spreadsheet.
GET https://us-central1-renew-proformas.cloudfunctions.net/renewApi/v1/health
Authorization: Bearer rnw_<key id>_<secret>
200 {"ok":true,"service":"renew-api","version":"v1","time":"…"}
401 the key is missing, wrong, revoked or expired
403 the key is not allowed to do that
429 more than the key's requests a minute (see Retry-After)
The health check is the only endpoint, on purpose: nothing real is exposed until Steele approves one.