Reviewing and revoking a connection

See which can act for you and what each one can reach, and revoke any of them. You need only your own sign-in; the page lists your own connections and no one else’s.

Review your connections

From your profile menu, open Profile, and in the AI clients () card select Manage connections. Connected clients lists one row per client you’ve connected.

Each row shows:

the client’s name, such as Claude or ChatGPT;
one badge per area it can reach, reading read or read / write, such as Planning & approvals · read / write;
when you connected it, when it was last used, and when the connection expires.

If you haven’t connected a client, or have revoked them all, the list says no AI clients are connected.

Revoke a connection

On the client’s row, select Revoke.
The dialog asks Revoke access for the client. Select Revoke access to confirm, or Keep connection to leave it.

The client loses access immediately, including any request already under way, and its row leaves the list. Its next request is refused, with the signal a client reads as “sign in again”.

When a connection ends without you

A connection is ended for you, as if you had revoked it, when:

you reset your password;
you set up or turn off a method, or an admin resets yours;
your workspace starts requiring two-step verification and you haven’t set it up;
an admin removes you from the workspace. Restoring your access later doesn’t bring the connection back.

A system admin can also review and revoke your connections: on the member list at Settings → Workspace → Members, the AI connections button on your row lists them, each with its own Revoke button.

Connect it again

To use a revoked client again, reconnect it from the client itself. It runs through sign-in and the consent screen again, and you choose its scopes afresh; see Connecting Claude, ChatGPT or a coding agent.

A connection you leave alone expires 90 days after you approved it, and the client then asks you to sign in and choose its scopes again, in the same way.

Revoking, like connecting and reconnecting, is recorded on the ; see How AI activity appears on the audit trail.