Manage existing connections
Inspect installation settings, manage credentials, and enable or disable connections.
Choose the control that matches your goal
Installation controls affect the workspace; personal access controls affect your own use of a connection. Confirm which scope you are managing before making a change. You need the admin role for installation settings, while personal access is managed from your own workspace.
- To stop your own use, open the personal connection and use Disconnect when available.
- To stop routing through the installation for everyone, use Disable installation in the Admin workspace.
- To limit which members can use an installation, edit its team scope.
- To change an organization-owned API token, use the credential controls in Connection settings.
View connection details
Click any connection from the Connections page to see its configuration, tool list, authentication status, team assignments, and recent activity.
Enable or disable a connection
Open Connection options, then Connection settings. Disable installation stops routing for the workspace and preserves its configuration. Re-enabling requires current readiness checks and, for production, a fresh billing preview.
Update connection settings
Connection settings displays Saved setup and installation status. For an organization-owned credential, administrators can save or revoke the API token there. Use the team scope editor on the connection page to change team access. Saved setup is a summary, not a general configuration editor.
Disconnect personal access or disable an installation
Use Disconnect in your personal connection to revoke your own access, or Disable installation in the Admin workspace to stop routing for everyone. These controls do not erase audit history. There is no connection-deletion control in this workflow.
Check the effect of disabling an installation
Disabling preserves the saved installation and its history while preventing normal routing through it. Confirm the disabled state in the Admin workspace and try the relevant read path from a member account; the disabled connection should not remain usable simply because a client cached its tool list.
A disabled connection no longer contributes enabled connection quantity. Previously measured transfer and historical billing events are not erased. If your goal is to investigate an incident, retain the relevant activity and provider evidence rather than treating disabling as deletion.
Re-enable with the current context
Treat re-enabling as a new activation decision. Check provider authentication, reviewed tools, the recent read-only test, team scope, and the current billing preview. An old readiness result may no longer match the connection you are enabling.
- Resolve the blocker shown by the setup guide.
- Repeat the read-only test with the intended provider identity and allowed resource.
- Inspect and accept the current activation preview.
- Verify a member’s read and its activity record after enabling.
When a saved setting needs a different value
Saved setup is a summary rather than a general-purpose editor. Use the controls that the connection actually exposes. Do not expect a display-name change, a personal disconnect, or an API-token update to rewrite the server endpoint or all authentication preferences.
For changes outside those controls, plan the appropriate replacement setup with the administrator and verify its access and billing impact before enabling it. Keep the existing installation identifiable in historical records.