Connections

When you authorise an external application from the browser —Claude Desktop and any other client that connects by signing in, as described in Connect your AI assistant— that authorisation is recorded here. The screen lives in your user menu, at the very bottom of the sidebar: Connections.

API keys do not appear on this screen: they belong to the organisation and are managed in Settings. Here you only find the authorisations you granted with your account.

What the list shows

• Application. The name the client declared when it registered. Careful: the application picks that name itself, so treat it as a hint, not as proof of identity. If it declared none, you will see its identifier.
• Organisation. The one you picked when authorising, and the one that decides which documents that connection sees.
• Granted permissions. What you accepted, in plain language: see your knowledge bases, search your documents, get download links…
• Granted. When you authorised that connection.

The same application can appear several times, once per organisation you authorised it in. That is normal if you belong to more than one and want to use it in several: each row is a separate authorisation, with its own organisation.

Revoking access

The Revoke access button on each row cuts off the authorisation. It asks for confirmation first, because there is no undo: the application will stop working until you authorise it again from within it.

Two important things about what happens when you revoke:

• It is revoked in all your organisations. Revocation is per application, not per row. If that same application was authorised in two organisations, it is disconnected from both, and the confirmation warns you when that is the case.
• Access already granted can keep working for up to 15 minutes. What stops immediately is the application getting fresh access; the access it already holds expires on its own. This is not a delay in the panel: in-flight permissions are checked without hitting the database, and promising you an instant cut-off would be a lie. Those 15 minutes are the maximum, and there is no way to shorten them from the panel.

Common cases

• I want to change a connection's organisation. It cannot be edited: revoke the access and authorise the application again, picking the other organisation.
• I no longer use that application. Revoke its access. A forgotten authorisation renews itself for as long as the application stays alive.
• I do not recognise a connection. Revoke it: if it was legitimate, the application will ask you to authorise again and you will find out then.
• The list is empty. You have not authorised any application through the browser yet. If you connected your assistant with an API key, that route does not create a connection.

When authorising

Before a connection shows up here there is an authorisation screen showing which application is asking and which permissions it wants. It is worth reading:

• Grant only what the tool needs. If a permission turns out to be missing later, the application itself will ask you to authorise again.
• If the application asks for access to your documents, you will have to pick an organisation, unless there is only one you can use. That choice also changes the panel's active organisation; the screen warns you before continuing.
• The name shown is chosen by the application itself, which is why it appears quoted with its identifier and its destination underneath: that is what really tells you who you are granting access to. If you landed on that screen without having asked for a connection, do not continue.

Updated on Aug 19, 2026