Approvals
Put chosen kinds of change behind a second person, and approve, reject or withdraw the changes that wait.
Approvals, under Configure, lets your organization require a second person for chosen kinds of change. A change of such a kind is not made when someone asks for it. It waits until another owner or admin approves it.
Choose what needs approval
Under What needs approval, tick the kinds of change and press Save:
- API keys: creating, changing, rotating or revoking a key.
- Members: adding, changing or removing a member, and transferring ownership.
- Projects and teams: creating, changing or deleting them, which includes their budgets, data policies and model lists.
- Routing policies: activating one.
- Webhooks, provider keys and telemetry: adding, changing or removing them.
- Organisation settings: the organization's settings, closing it, and erasure.
Approvals need at least two owners or admins; with fewer, saving is refused. While any kind is ticked, changing this list is itself a change that needs approval, so one person cannot turn approvals off alone. Owners and admins can change the list.
When a change waits
Asking for a change of a ticked kind, in the console or with an API key, gives the message Sent for approval instead of making the change. The API answers with status 202 and the waiting request. An approval.requested event goes to your webhooks.
The Waiting list shows each change: what it is, the request as it was asked, who asked and when it expires. A change waits a week.
- Approve makes the change at that moment, in your name, after every check it would meet, and says whether it succeeded. If the change creates an API key, the key is shown to you once: give it to the person who asked. Nothing the change answered is stored.
- Reject asks why; the person who asked sees your reason.
- Withdraw is offered to the person who asked, in place of approving.
You cannot approve a change you asked for, and you can approve only a change your role could make itself. All lists every change with its outcome.
Security settings
Require two-factor sign-in, set the session length, restrict the console to your network, and give new API keys a default expiry.
Single sign-on and SCIM
Connect your SAML or OIDC identity provider, verify your email domains, map groups to roles, enforce single sign-on and provision members from your directory.