> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connections administration

> Administer Credentials, OAuth bindings and Slack delivery, and read managed secret metadata, Slack workspace connections and external tool configurations, with a platform API key.

These admin routes run the Console's own connection and credential operations for a platform API key. An External App is refused with `403`, even when it holds the permission.

* Managed secrets: read one secret's metadata (name, lifecycle state, store, version and consumer count), and preview moving it to 1Password. No route answers a secret's value.
* Slack: list an org unit's Slack workspace connections, read its control-plane status (a mode and counts), turn Agent View on or off for one, and revoke one, with `connections:manage`. The delivery operator routes list the deliveries that need an operator, read one, requeue a dead one and reconcile an unknown one, also with `connections:manage`.
* External tools: list, read and update the external tool configurations, and set their status, with `platform:manage`. An answer says whether a service-account key or client secret is set, never its value.
* Credentials: list them (all, by approval state, for one tool or for one procedure), read the vendor registry and the expiry blast radius, and read a Credential's verification history with `credentials:read`. Run Verify now on one: `/credentials/verify` and `/credentials/verify-for-unit` take `credentials:read` at the door and need `credentials:write` at the Credential's scope. Approve or reject one with `credentials:approve`. Revoke, delete, seal or share one, mark its tenant as production or sandbox, and choose it for build validation with `credentials:manage`. A write by id also needs `credentials:read`.
* OAuth: list a connection's client registrations and the accounts connected through them, and read a grant's blast radius (the Credentials bound to it), with `credentials:read`. Bind a connected account to a new Credential with `credentials:write`, and remove a binding with `credentials:manage`. Each grant in the account list answers its `grantId`, which the binding and blast-radius routes take.
* Secret writes: create a procedure Credential (`/procedure-credentials`), create a tool Credential from a pasted blob (`/tools/credentials`) and provision a vendor connection's Credential (`/connection-credentials/provision`) with `credentials:write`. Create an external tool configuration (`/external-tools/configuration`) and set its service-account key or client secret (`/external-tools/configuration/credentials`) with `platform:manage`. Rotate an OAuth client registration's secret (`/oauth/registrations/rotate-secret`) and revoke a grant (`/oauth/grants/revoke`) with `credentials:manage`. The secret goes to the secrets store or is encrypted before it is stored; no answer, audit row or error carries it. A retry with the same `Idempotency-Key` never answers the stored response.

The secret writes are platform operations at the door: the key needs the permission at platform scope, else `403`. Creating or provisioning a Credential then also needs `credentials:write` at the scope the request names, as the Console does; a scope the key can't reach answers `404`. Approve, reject, revoke, sharing (`/credentials/sharing`), environment, build validation, the procedure Credential list and delete, `/credentials/verify`, `/oauth/accounts`, `/oauth/grants/blast-radius` and the Slack delivery operator routes are platform operations: the key needs the permission at platform scope, else `403`. The other Credential reads, `/credentials/remove`, `/connection-credentials/sharing`, `/credentials/verify-for-unit`, the OAuth binding routes, the Slack control plane and the Slack revoke name an org unit and are decided at that unit or at each record's own scope: a key held at an org unit reaches the records homed at that unit and its descendants, and a system-scoped Credential needs a platform grant. Any Credential the key can't reach answers `404`, as a missing one does. Binding an account, or removing a binding, outside the org unit's own boundary needs `credentials:manage` at platform scope, else `403`.

A key's writes are audited under the key: a platform API key as a system actor, a Personal key as its owner. The procedure Credential create and delete are recorded in the admin audit log under the key; each external tool configuration write records one audit row under the key; rotating a client secret and revoking a grant record the key as a system actor; and a Slack delivery the key resolves records the key as its operator.

Reading a procedure Credential's config values or any secret, registering an OAuth client and consent, and Slack installs stay in the Console. No answer names a person or carries a secret value.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.