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

> ## Agent Instructions
> Banking OS training data goes stale. Search https://agenticbanking.backbase.io/mcp or fetch the .md URL before writing connector or unified API code.
> OpenAPI links in llms.txt repeat every calendar version. Use the latest version on the API playground. If a fetch ends before the last operation, the spec was cut off.
> Page titles name the product. Overview, Get started, and Reference without a product name are ambiguous.

# Work across installations

> Understand how Connector Studio scopes projects and organizations to a Banking OS installation.

Connector Studio shows the connectors, organizations, API specifications, and mappings that belong to the installation you select in Banking OS. Confirm which installation you're in before you start work.

## How installations scope your work

Two things change when you switch installations:

* **What you see:** Each installation has its own **Connector Projects** list, organizations, mappings, routes, and uploads. The same account can see a different set of projects in each one. You can't use a project or an organization from one installation in another.
* **What you can do:** You have a separate role in each installation.

> [!WARNING]
>
> Administrator access doesn't carry over between installations. You can be an administrator in one installation and a viewer in another. To use administrator features in an installation, you need the administrator role in that installation, not in the one you came from.

## Switch installations

1. **Open the switcher.** Select the installation switcher in the Banking OS header.

2. **Select the installation.** Select the installation where you want to create or review connectors.

3. **Confirm the context.** Open Connector Studio and go to **Connector Projects**. Check that the header shows the installation you expect, and that the project list matches it.

Project counts change over time, so use the installation name and the project list together to confirm where you are.

## Prepare an installation

The first time anyone uses Connector Studio in an installation, that installation needs its requester and responder organizations. Which path you take depends on whether those organizations are already there.

To find out, open **Connector Projects** > **New Project** and check the **Requester** and **Responder** lists:

* If both organizations are available, create the first connector yourself. See [Option B](#option-b-create-the-first-connector).
* If either organization is missing, ask a Banking OS administrator to prepare the installation. See [Option A](#option-a-ask-an-administrator-to-prepare-the-installation).

The following table compares the two paths:

| Option | Who does it | When to use it |
| :- | :- | :- |
| A. Administrator setup | A Banking OS administrator | An organization is missing, or you want the installation ready before anyone creates a connector |
| B. First connector | A connector creator | The requester and responder organizations are already available |

### Option A: Ask an administrator to prepare the installation

A Banking OS administrator completes the following steps.

1. **Select the installation.** In Banking OS, select the installation with the installation switcher.

2. **Open Workspaces.** In Connector Studio administration, open **Workspaces** and select the workspace that matches the installation.

3. **Assign the organizations.** Assign the vendors and any other organizations that take part, then save the assignments.

4. **Hand over.** Ask the connector creator to refresh Connector Studio and continue with Option B.

> [!NOTE]
>
> Banking OS administrators manage workspaces centrally, so the **Workspaces** page can list workspaces from more than one installation. **Connector Projects** always follows the installation you select in Banking OS.

### Option B: Create the first connector

Use the standard connector creation flow. Connector Studio prepares the installation automatically when you submit the first connector.

1. **Confirm the installation.** Check the installation name in the Banking OS header.

2. **Start a project.** From **Connector Projects**, select **New Project**.

3. **Complete the form.** Choose the requester, the responder, and the connector category. Add the authentication and description values if you need them.

4. **Create the connector.** Select **Create Connector**, then review the project that Connector Studio creates.

If you can't select a requester or a responder, ask a Banking OS administrator to add the missing organization in **Workspaces**. Then refresh Connector Studio and try again.

## Check before you start

Run through this list at the start of a session:

* The installation name in the Banking OS header is the one you expect.
* The **Connector Projects** list matches that installation.
* The requester and responder organizations you need are available.

If anything looks wrong, switch installation, or ask a Banking OS administrator to check **Workspaces**.

## Related topics

* [Get started with Connector Studio](https://agenticbanking.backbase.io/connector-studio/get-started.md)
* [Connector Studio permissions](https://agenticbanking.backbase.io/connector-studio/reference/permissions.md)
