> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/organization-connector-credentials.md).

# Organization connector credentials

An organization connector defines how StackAI authenticates with a provider. It can contain an OAuth application ID, application secret, and permission scopes. Connections use this configuration to authorize individual accounts.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FpHGopbNWuxLam6jIuG8z%2FG047.mp4?alt=media&token=f8b7ecc6-e929-45e8-90b2-85dba030a4d3>" %}

## Before you start

You need access to connector settings in StackAI and permission to register or configure an application with the provider.

## Choose the connector type

Open Settings → Connectors and select the provider.

![Provider connector type selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/K1NnB8t4piJ2jID8gARS/assets/g047-g047-01-provider.png)

Review the existing connectors before creating another organization configuration.

Select New Connector and choose the required authentication type.

![Provider connector type selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/VvMQP6BHgUBEXiO5fr95/assets/g047-g047-02-oauth.png)

The available methods depend on the provider.

Give the connector a recognizable name.

![Provider connector type selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/RBwwI2E3MU5YTkl3x0sy/assets/g047-g047-03-identity.png)

Distinguish its purpose from other configurations for the same provider.

## Review the application requirements

Read the setup requirements, including the callback URL, scopes, and credential fields.

![Connector application setup requirements](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/FRB5palOBRKSy8Q0j5YE/assets/g047-g047-04-setup.png)

Copy the callback shown by StackAI rather than constructing one yourself.

## Configure the provider application

Configure the application in the provider's console and enable the required API.

![Provider application authentication settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/5gqDrblcRAQQNu3hTTuw/assets/g047-g047-05-provider-api.png)

Set its audience and authorized users according to the provider's application requirements.

Choose the permissions required by the intended actions.

![Provider application authentication settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/72WmTpPIPHJtUHFixqRi/assets/g047-g047-06-scopes.png)

Compare the provider's scope configuration with the requirements shown in StackAI.

Create the appropriate OAuth client and register the exact callback URL.

![Provider application authentication settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/xtcGx3rpZUOxAoVvmnxN/assets/g047-g047-07-client.png)

Keep its client secret in the designated credential fields rather than in shared documentation.

## Save the credentials in StackAI

Enter the provider-issued client ID and secret in the corresponding fields and complete setup.

![Provider credential configuration fields](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/817BDUKxOt1qT12QRciU/assets/g047-g047-08-credentials.png)

The connector must use the values from your registered application.

## Connect an account and use an action

Return to Connections and authorize an account through the new connector.

![Provider account connection verification](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/4LENJafCecRnKPsQy9JA/assets/g047-g047-09-connection.png)

The organization connector defines the application. The account connection provides a user's authorization.

Review the connector's account connections and enabled actions.

![Provider account connection verification](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/4iuAonI6Pmp9ZzKaDgSo/assets/g047-g047-10-verify.png)

Run a representative action to confirm that the configuration supports the intended operation.

## Important behavior

Register the exact callback URL shown by StackAI. A mismatch can prevent authorization.

Store application secrets only in the designated credential fields or approved secret storage.

## Continue

* [Create and manage connections](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/create-and-manage-connections.md)
* [Custom OAuth scopes and reauthorization](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/custom-oauth-scopes-and-reauthorization.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/organization-connector-credentials.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
