Admin and security glossary

Links on this page to features marked Preview describe designs that are not available yet.

Terms for organizations, access control and data protection. Shorter definitions of the core API terms are on the main Glossary.

A record of everyday product use for compliance, such as a message sent or a file uploaded. See list.

A key starting sk_admin_ that manages the organization through /v1/organizations/* and cannot call models. See admin keys.

A record of an administrative action: who, what, when, from where, with before and after values. See audit logs.

Customer-managed encryption keys: stored data is encrypted under a key in your own cloud key service. See cmek.

An Admin key carrying the compliance:read scope. See compliance api.

Where requests are processed and data is stored: us, eu or global. See data residency.

The highest role a member holds in a workspace, counting their own and their groups’ roles.

What happens when the inference hook does not answer: closed refuses, open allows and logs.

A set of members granted workspace roles together. See groups.

Your own service that approves or denies each request before the model runs. See inference hooks.

Addresses a key may be used from. See api keys.

The identity provider that signed a workload’s token, identified by its iss URL. See list issuers.

An instruction to preserve named people’s records beyond normal retention. See create.

The background job that moves stored data to a new key after rotation.

A workspace setting that stops requests from choosing another region.

A standard your identity provider uses to create, update and remove members and groups automatically.

A non-human identity that owns keys and trust rules for automation. See service accounts.

Trading an external OIDC token for a short-lived Syntic token at POST /v1/oauth/token. See workload identity.

Conditions under which an external identity token may act as a service account. See create trust rule.

A division of an organization with its own keys, limits, spend and data. Every API resource belongs to one. See workspaces.

Was this page helpful?