When you connect Claude, ChatGPT, Cursor or dip to your tenant, you approve it once and it keeps working without asking you again. Settings → Connected apps lists every one of those approvals that is still live and lets you end any of them. Every member can open this page; it needs no privilege.

Your connections

Each row is one app you approved: If nothing is connected, the page says “No AI tools are connected to this workspace yet.” An app approved without Stay connected holds only a short-lived sign-in (at most 15 minutes) that it cannot renew, so it is not listed here; it stops on its own.

Revoking a connection

Click Revoke on a row and confirm. Revoking is safe to repeat.
  • The app can no longer renew its sign-in, at once. It would have to be approved again.
  • A connection whose name is not marked unverified belongs to the platform: a query engine’s or an app’s own sign-in. That engine checks its sign-in itself, so it can keep working for up to 15 minutes after you revoke it. The page’s confirmation says so.
  • An access token the app already holds stops working within about a minute. It is not cut off in the same instant. A query-engine sign-in the app already made from it is checked by the engine itself, so that one can keep working for up to 15 minutes.
  • For dip, the next command that calls the tenant is refused. Sign in again with dip login. A push credential that dip app push already obtained is checked by the registry itself, so it stays valid for up to 15 minutes.
To use the app again, reconnect it from the app and approve it on the consent screen. A connection you revoked only moments ago cannot sign back in for a few seconds: if the app says “this connection was revoked”, wait a few seconds and try again. Revoking a connection ends only that connection. It does not change your roles, and it does not touch service-user API keys; revoke those under Settings → Service users.

Members’ connections

If your role holds Members · read, the page also shows Members’ connections: the same list for every other member, with the member’s email. If your role also holds Members · delete, each row has a Revoke button. Use it when a member loses a laptop or approves an app you don’t recognise. See Roles and permissions for which built-in roles hold these. If the list can’t be loaded, the page says so and offers Try again; an error is never shown as an empty list. Each list shows the 500 newest connections and says so when there are more.

Removing a member

Removing a member cuts every connection they approved. Their apps can’t renew, and any access token they hold is refused within about a minute with a message that the membership was removed. A query-engine, app or registry sign-in already made from one is checked by that engine or registry itself, so it can keep working for up to 15 minutes, as for a revoke. Reconnecting does not help; an administrator has to invite them again.