PermuteDocs
Go to Permute

Identity and access

Sessions and connections

Review connected browsers, CLI logins, and MCP clients, and end access you no longer need.

Manage connections and browser sessions

Open Your Profile → Connections to review browser, CLI and MCP logins across organizations. Filter by type and by All, Connected or Inactive (expired and disconnected logins). Browser entries identify the platform or hosted app and mark your current login as This session. Sign out ends one browser login and its ability to renew; signing out the current session returns you to sign-in. Other logins stay active.

Organization administrators can review their organization’s CLI and MCP logins in People & access → Connections. View access shows the resources and permissions approved for that connection; current permissions still apply. Disconnect ends one login and its renewal without changing MCP connector settings. Browser sessions remain personal because a platform login can span organizations.

Understand approved access

A CLI or MCP connection can use only its approved resources and permissions within your current access. Approving a connection does not give you new resource permissions. If your access is revoked, the connection cannot keep using that resource through an earlier approval.

To change who can use a resource, update its permissions. To end one client’s login, disconnect that connection. Deleting an MCP connector also invalidates its MCP sessions; see MCP access.

Review other credentials

Signing out or disconnecting a login does not pause an approved Business Action schedule. To stop future scheduled runs, pause its trigger. See caller access and automation access for how login access and automation authority differ.

API keys have their own grants and revocation controls (they are separate from browser, CLI, and MCP logins). Review API keys when offboarding someone or ending automated access. Apps also retain their own grants until those grants are changed or revoked.