--- title: "Share connectors across workspaces" slug: "share-connectors-across-workspaces" updated: 2024-07-23T13:53:43Z published: 2024-07-23T13:53:43Z canonical: "support.tulip.co/share-connectors-across-workspaces" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Share connectors across workspaces ## Overview Connectors and their Connector Functions are critical assets for the functioning of your operations. In some cases, it makes sense to share these assets across Workspaces. **Examples** - Every workspace should be reporting defects to the same SQL table, with the same format, so the connector writing to that table should be shared - Every workspace is interacting with our global SAP instance, I want to share this asset across workspaces In other cases, Connectors really only make sense in the context of one workspace. **Examples** - Facility 1 is the only facility that uses lifeX andon lights, so sharing that connector with other sites doesn't make sense - Facility 2 is adopting a new warehouse management system, but this system hasn't been rolled out to other facilities - Facility 1 has their own credentials to talk to the shared SQL database ## How to Use Note Historically all connectors were shared across workspaces, when connectors across workspaces is enabled, all existing connectors will set to `global` to maintain behavior. ### On Creation On creation, new Connectors are scoped only to that Workspace. This is indicated by the absence of the globe icon next to the connector name: ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28117%29.png) ### Share with another Workspace To share this connector with other Workspaces: 1. Select **"..."** menu next to the connector. 2. Select **Assign**. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28114%29.png) 3. Pick which workspaces you would like to share this connector with, or select a single workspace to move this connector to. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28113%29.png) 4. Click **Assign**. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28115%29.png) When `All Workspaces` is selected, that connector is exposed in the connectors page in all workspaces. When a specific workspace is selected, it only appears within that workspace (and disappears from the original source workspace). ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28118%29.png) ## Further Reading - [What are Workspaces?](/r230/docs/what-are-workspaces-1) - [Connectors](/r230/docs/connectors) - [SQL Connectors](/r230/docs/sql-connectors) **Connectors** **Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions. - **HTTP Connectors** utilize HTTP API endpoints. - **SQL Connectors** can enable connectivity with certain SQL databases. - **MQTT Connectors** can connect to MQTT brokers for machine monitoring. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif) **Connector Function** **Connector Functions** are individual operations to interact with an HTTP or SQL Datasources. Connector Functions can have inputs and outputs, and can be called from: Triggers, Functions, Automations, and AI Agents. Once pulled, data can be used throughout your applications. **Workspace** **Workspaces** are a model within Tulip to separate Tulip assets to match the places where work is being done. A workspace should represent a single facility, line, or department. With workspaces, users across facilities can easily collaborate, share their solutions, and improve their global operations.