Skip to main content
An auth connection stores the authentication configuration used by supported external-service requests. It is separate from your dashboard sign-in and from the personal API key used to access Threetone.

​
Supported manual methods

These are manually configured service credentials. Selecting an OAuth method here does not create an interactive user consent flow or enable a native connector that is absent from the catalog.
Recording pending for workspace auth connection configuration. No playable video is available yet.

Recording pending: Configure and review a workspace auth connection. Follow the written guide below.

​
Create a connection

1

Choose the intended workspace

Open Agent Settings and find Auth connections. Use a workspace account permitted to manage these credentials.
2

Choose the method

Select Add auth and the method required by the provider. Enter a useful Name, review the Provider field, and supply the required configuration. Use the provider’s current documentation for scopes, claims, and token parameters.
3

Save and read back

Select Create auth connection, then reopen the saved entry and inspect the non-secret metadata. Retain the connection ID for supported references. Do not expect the raw credential to appear in the list or edit form.
Screenshot pending for workspace auth connections. This illustration is not a product screenshot.

Screenshot pending: Auth connections in Agent Settings and a manual connection form with all private fields hidden.

​
Reference and update

Select the saved connection in a supported MCP or tool field, or use its identifier in a supported environment value. Creating a connection does not attach it to every agent or grant resource access to every member. For a manually managed connection, use its actions menu and Edit connection when permitted. Confirm the metadata and changed fields before Save changes. Empty secret fields keep the existing values in the supported edit workflow. Do not treat an empty field as a request to clear a credential. Provider-managed native connections must be managed through their integration workflow. Review dependencies before deletion or rotation. If the edit is rejected because the resource changed, refresh and reconcile with the current version instead of repeatedly overwriting it.

​
Verify the external boundary

Credential storage is separate from successful authentication to a provider and successful tool execution. When the intended request path is available, test a harmless operation against the approved provider endpoint, inspect its outcome, and verify that an incorrect or revoked credential fails. Do not use a production mutation as a connection test.

​
Frequently asked questions

No. Auth connections authenticate supported requests to external services. Use Access and credentials for Threetone’s API and session boundaries.
The form does not retrieve raw stored secrets. Leaving a secret field empty preserves its current value in the supported edit workflow. Enter a new value when intentionally replacing it.
Its management type and permissions determine the available actions. Use the native integration workflow for provider-managed connections.