> For the complete documentation index, see [llms.txt](https://studio-docs.japan-ai.co.jp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.japan-ai.co.jp/en/administration-and-operations/configure-shared-connections.md).

# Configure Shared Connections for a Project or App

When a Project or App uses the same external service, an administrator prepares a **shared connection** and assigns it to the App when needed.

This article explains how to register a shared connection and configure it under an App's "App-wide connectors." For choosing between types, see [Choose Between Personal Connections, Shared Connections, and Secrets](/en/administration-and-operations/choose-personal-shared-connections-and-secrets.md). For expiration and reauthentication, see [Handle Expired Connections and Owner Changes](/en/administration-and-operations/handle-expired-connections-and-owner-changes.md).

## Before you begin

* Check the correct organization and target Project or App. Do not confuse environments.
* Check permission to change connection settings and App-wide settings. Being able to open the target does not necessarily mean you can create or assign a shared connection.
* Decide the connection destination, purpose, data, and execution scope.
* Prepare an account for the external service that is approved for team, department, or business use. Check external service terms and organization operations before using a personal account for shared use.
* Decide the authentication owner, connection administrator, and contact for expiration.

> Processing that uses a shared connection is affected by the permissions of the authentication account at the external service. Use a business account with minimum required permissions, and do not casually share personal permissions.

Screen entry points and operation scope vary according to organization settings, permissions, and App configuration. If an item is not shown, do not create another connection; ask the responsible administrator.

## Separate connection users from the authentication account

For a shared connection, distinguish these three parties.

| Category                     | Who                                                                       | What to check                                                                                           |
| ---------------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Person who configures it     | Administrator who creates and assigns the connection                      | Whether they can manage the target Project/App, service, connection type, and configuration result      |
| User or process that uses it | Users or automated processes using Agents, Workflows, or business screens | The feature that uses the shared connection, executable operations, and users' access scope             |
| Authenticated account        | Business account that signs in or authenticates at the external service   | The account's data scope, execution permission, and management responsibility on expiration or transfer |

Configuring a shared connection does not grant management permission to users. On the other hand, when users run processing using a shared connection, reading, sending, or updating at the external service may occur with the authenticated account's permissions. Check both user access permissions and external service account permissions.

## 1. Open Project "Connector Settings"

1. Open the target Project, then open **"Connector Settings"** from the settings screen. If there is an App-wide requirement, you may also be able to open connection settings from **"Settings"** in the target App.
2. Check **"Project connectors."** Connections there are candidates for shared use in the Project.
3. Check existing connections for the same service, their names, authentication accounts, purposes, and connection types.
4. If candidates available from the organization are displayed, also check **"Organization-wide connectors."** However, whether you can choose an organization-wide candidate or it is copied to the Project varies by permission and configuration.

Do not duplicate connections for the same service; check existing connections before adding one.

## 2. Add or copy a shared connection

If you cannot use an existing candidate, add a connection to the Project.

1. Select **"New connector."**
2. Select **"Project connector."** On a screen that displays connection types, check that it is a **"Shared connection."**
3. Select the external service from the list. Do not substitute another service for one that is not displayed.
4. Give the connection a name that identifies its purpose and authentication account. Example: `Sales shared_inquiry handling`. Do not include secret values such as passwords, API keys, or tokens in the name.
5. If an external service authentication screen opens, sign in with an approved business account, check requested permissions, and authenticate.
6. Return to the Project and check that the connection appears in "Project connectors" and that its service, name, and connection type are intended.

When using an existing personal connection from a candidate list, **"Copy"** or **"Copy and configure"** may appear. Before doing so, check whether the source external account can be shared and whether it remains manageable after the owner changes.

> Even if a connection name appears to be for shared use, that does not make the external service account permissions safe. Check the account used for authentication, OAuth consent contents, and permissions for target data. Do not paste credentials into chat, procedures, or similar materials.

## 3. Assign it to an App shared requirement

When an App requires a shared connection, creation in a Project alone may not complete the setup. In App settings, select and assign the required connection.

1. Open the target App and check connection requirements from **"Settings."**
2. In **"App-wide connectors,"** check services that are not set and their status. Statuses may include **"Not set,"** **"Checking,"** **"Configured,"** **"Disabled,"** and **"Stopped."**
3. Select the configuration action for the target service, then select the shared connection checked in step 2 from **"Connectors available for this App."**
4. Select **"Configure"** and wait for completion to appear. To use an organization-wide candidate, select it from **"Organization-wide connectors,"** then check and execute the displayed **"Copy and configure."**
5. Return to the App connection requirements and check that the target service is **"Configured."**

If "Connector was created, but configuration for the App failed" appears, do not recreate the same connection. Select the created connection and configure it again. If "This connector's sharing scope does not match the App's requirements, so it cannot be connected" appears, check whether you confused a personal and shared connection or the target Project.

## Which connection an Agent or Workflow selects

Connection selection is not determined solely by the person operating the screen. Handling of shared and personal connections varies according to where the Agent or Workflow runs and the type of connection required by the App.

| Execution situation                                             | Guideline for connection selection              | What an administrator checks                                                                       |
| --------------------------------------------------------------- | ----------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Test an Agent or Workflow in a Project                          | A personal or shared connection may be used.    | Do not conclude from the test result alone that the same connection will be used after publishing. |
| A user operates an Agent or business screen in an installed App | Required connections vary by App configuration. | Check guidance such as "Connection required."                                                      |
| Workflow or automatic execution in an installed App             | A shared connection may be required.            | Check whether the account can be used with no executor present and check send/update destinations. |

Even for the same external service, required connections can differ between Agents and Workflows and between manual and automatic execution. Having a shared connection does not necessarily mean that every user no longer needs personal authentication. Guide users who need a personal connection to [Connect Your Own External Accounts](/en/administration-and-operations/connect-your-external-accounts.md).

> If automatic execution uses a shared connection, processing at the external service may occur with the shared authentication account's permissions rather than the executor's own permissions. For email sending, record updates, file changes, and similar operations, check the target and result with a small amount of approved data before expanding use.

## 4. Check operation and management responsibility before use

Separately check configuration status and actual processing.

1. Identify the Agent, Workflow, or App business screen you plan to use.
2. Prepare approved test data and a safe send or update destination.
3. Check user operations and, if there is automatic execution, its processing, each in a small scope.
4. In the external service, check that the data read, destination, update destination, and result are intended.
5. Record the connection name, target, purpose, management owner, and contact. Do not record actual values.

Even when it is "Configured," it can fail because of insufficient permission at the external service. Do not treat merely opening the screen as readiness to use it; check a representative operation.

## If something does not work

| Situation                                                   | What to check and do                                                                                                                                                                                                                                                                         |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "Connector Settings" or "New connector" is not displayed    | Check whether it is the correct organization/Project and whether permission and feature availability conditions exist to manage shared connections. Do not substitute a personal connection for a feature that is not displayed.                                                             |
| "You do not have permission to change this setting" appears | Check permission to create connections and assign an App-wide connection, then ask an administrator with permission.                                                                                                                                                                         |
| The App remains "Not set" or "Checking"                     | Do not stop after creating the connection. Check that you assigned it under the App's "App-wide connectors" and display the status again.                                                                                                                                                    |
| It says the sharing scopes do not match                     | Check that you selected a shared rather than personal connection, that it belongs to the target Project, and that it is the service required by the App.                                                                                                                                     |
| It becomes "Disabled" or "Stopped"                          | Check the external service account, consent, expiration, and management status. Do not repeatedly disconnect or recreate it; for expiration handling, see [Handle Expired Connections and Owner Changes](/en/administration-and-operations/handle-expired-connections-and-owner-changes.md). |
| An Agent or Workflow fails                                  | Check the feature that ran, when personal or shared connections are used, external service permission, target data, and the error at execution.                                                                                                                                              |

For an inquiry, include the organization name, Project or App name, connection destination service, connection name, operation time, displayed status/message, target Agent/Workflow, and operations already checked. Do not send passwords, API keys, tokens, or confidential information from authentication screens.

## Checklist

* [ ] I checked the correct organization, Project or App, and connection destination service
* [ ] I checked that I have permission to configure and assign a shared connection
* [ ] I selected an approved business account and checked minimum required external service permissions
* [ ] I checked "Project connector" and "Shared connection" and registered or copied it
* [ ] In the App, I assigned the correct connection under "App-wide connectors" and checked "Configured"
* [ ] I checked connection selection for Agents, Workflows, and automatic execution, and users who need personal connections
* [ ] I checked results in the external service within the approved scope
* [ ] I recorded the management owner, purpose, dependent Projects/Apps, and contact for expiration

## Next articles to read

* Choose a connection type: [Choose Between Personal Connections, Shared Connections, and Secrets](/en/administration-and-operations/choose-personal-shared-connections-and-secrets.md)
* Check initial App setup: [Complete the Initial Setup of an App](/en/use/complete-app-setup.md)
* Connect your own external account: [Connect Your Own External Accounts](/en/administration-and-operations/connect-your-external-accounts.md)
* Handle connection expiration and owner changes: [Handle Expired Connections and Owner Changes](/en/administration-and-operations/handle-expired-connections-and-owner-changes.md)
