​

Permissions and safety

A connected app never holds a password or a long-lived secret with fixed powers. Its token proves who you are; what it may do is looked up on every request. That is why every control below takes effect immediately, without reconnecting the app.

​

Account Settings → Connected apps

Open it from your avatar menu (top right) → Account Settings → Connected apps. These are your own apps, across every project. One row per app. For each you can:

• Toggle Deploy. Off means read only. On lets the app use the deploy tools.
• Edit projects. Limit the app to some of your projects. It will not see the others even though you can.
• Revoke. The app loses access on its next request and has to sign in again from scratch.

​

Per-project opt-in

Deploy tools also require the project itself to allow agent writes. A project owner or administrator turns that on in the project’s Settings → General → Agent write access. Until then, every app is read only on that project regardless of its own switch. Two switches, two people: the person who connected the app decides whether that app may deploy; a project admin decides whether any app may deploy on that project.

​

Your role still applies

An app acts as you. If you are a read-only member of a project, no switch makes the app able to deploy there. Owners, administrators, and developers can.

​

Production asks first

Rebuilding, restarting, updating modules on, or backing up a production deployment always returns confirm_required. The agent must call again with confirm: true. Well-behaved agents ask you before doing that.

​

What is never possible

No connected app can delete a project or deployment, restore a backup over a database, change domains, manage servers, open a shell, or change billing. These are not gated; they do not exist as tools.

​

Audit

Every write made through an app appears in the project’s audit log, attributed to the app and the user who connected it.