> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure authenticators

> Create and manage authentication credentials for third-party integrations.

## Overview

Authenticators store the credentials Go Autonomous needs to connect to your external systems. Before setting up a [connector](/knowledge-base/administration/connectors), you typically need to create an authenticator with the right credentials — API keys, login information, or OAuth tokens.

## Create an authenticator

<Steps>
  <Step title="Open Authenticators">
    Navigate to **Administration > Company Settings > Authenticators**.
  </Step>

  <Step title="Click Get started or Add">
    If this is your first authenticator, click **Get started**. Otherwise, click the add button to create a new one.
  </Step>

  <Step title="Choose the authentication type">
    Select the type of authentication your external system requires — API key, basic authentication (username/password), or OAuth.
  </Step>

  <Step title="Enter your credentials">
    Fill in the required fields. This varies by authentication type:

    * **API key** — enter the key and any associated identifiers.
    * **Basic auth** — enter the username and password.
    * **OAuth** — configure the OAuth flow with client ID, secret, and token endpoints.
  </Step>

  <Step title="Name and save">
    Give the authenticator a clear name (e.g., "SAP Production API Key" or "Salesforce OAuth") and save.
  </Step>
</Steps>

<Warning>
  Authenticator credentials are sensitive. Only administrators should have access to create and manage them. Make sure credentials have the minimum required permissions for the integration.
</Warning>

## Managing authenticators

From the Authenticators page, you can:

* View all configured authenticators.
* Edit credentials when they change (e.g., rotating API keys).
* Delete authenticators that are no longer in use.

<Note>
  If you delete an authenticator that's in use by an active connector, that connector will stop functioning until a new authenticator is assigned.
</Note>

## What's next

* [Set up connectors](/knowledge-base/administration/connectors)
* [Manage organization settings](/knowledge-base/administration/settings)