> ## Documentation Index > Fetch the complete documentation index at: https://docs.threetone.in/llms.txt > Use this file to discover all available pages before exploring further. # Auth connections > Create reusable workspace authentication configuration, reference it from supported fields, and review safe credential changes. 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 | Method | Required preparation | | - | - | | Basic Authentication | The provider's username and password requirements. | | Bearer Token | A provider-issued token with the intended access. | | OAuth2 Client Credentials | A client ID, client secret, token URL, and provider-required token parameters. | | OAuth2 JWT | The provider's signing algorithm, key, claims, and expected token placement. | 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. ## Create a connection Open [Agent Settings](https://threetone.in/app/agents/settings) and find **Auth connections**. Use a workspace account permitted to manage these credentials. 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. 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. ## Reference and update Select the saved connection in a supported MCP or tool field, or use its identifier in a supported [environment value](/agents-platform/deploy/environment-variables). 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](/agents-platform/configure/authentication/overview) 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. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.