--- title: Approvals description: When your coding agent asks for something only a person may allow, you approve it in the portal with your passkey, and it runs once. --- # Approvals Your coding agent can ask for the sensitive things too: deleting or suspending an app, rolling back, restoring a backup, exporting a database, linking a GitHub repo, or anything else your organisation says needs a person. It cannot do them on its own. Instead it asks, and a person approves. ## What happens 1. **The agent asks.** Kaviris keeps the exact request the agent made and answers it with `pending_approval`, a request id and a link. The agent gives you the link. The owners of the organisation are notified too. 2. **You read it.** The link opens the request in the portal under **Approvals**: a sentence in plain language ("ulf@example.com via Claude Code – laptop wants to put a contract change in force on app shop"), and below it exactly what will run. For a contract change you also see what changes: new outbound hosts, databases, ports. 3. **You approve with your passkey,** or reject. Approving asks for your passkey again, even though you are signed in. That check is tied to this one request: it cannot be reused for another. 4. **It runs once, as you.** Kaviris runs the stored request (not anything the agent sends later) with your rights, once. If you no longer have the right to do it, or the agent's key was revoked in the meantime, nothing runs. The agent can check the outcome (`get_change_request` in MCP, or `GET /v1/change-requests/{id}`): pending, approved, rejected, expired or applied. ## Rules - **Only a person approves**, in the portal, with a passkey. An agent never approves, not even its own request. - **You must hold the right yourself.** A member cannot approve deleting an app, because members cannot delete apps. Requests you cannot approve are not shown to you as waiting. - **Your own agent's request** you may approve yourself, with your passkey: that is you, in person. - **Nothing changes after the agent asks.** The request is stored with a fingerprint (SHA-256) and cannot be edited. If the thing it refers to changes before you approve (say the agent edits the contract draft again), the old request fails instead of applying something you did not see. - **Requests expire** after 72 hours. An expired request cannot be approved. - **Every step is recorded:** who proposed, through which agent key, who approved or rejected, and what ran. ## Which actions need approval Each permission has a default. Owners can change it under **Settings → Approvals**: require approval for more (for example every contract approval), or for fewer. Some always need a person and cannot be turned off: deleting and restoring, linking GitHub, giving support access, and anything that manages members, roles, groups, policies, billing or the organisation itself. A few things are never done by an agent at all, approved or not: connecting the GitHub App, and downloading a database export (the download goes only to a person). For a contract change that adds a host Kaviris does not recognise and your code does not mention, the agent gets `pending_approval` with a link to the app: a person approves the contract change there. See also [Agent keys](agent-keys.md).