> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-administrators/organization/shared-connectors.md).

# Shared connectors

Connectors registered once for the whole organisation. Found under **Organization management → Shared connectors**.

## Why share a connector

A [connector](/en/for-administrators/assistants/connectors.md) can be added to a single assistant. That is fine for one assistant, and unmanageable for ten: the same server URL, the same credentials and the same decisions about which actions are allowed, repeated everywhere, drifting apart over time.

A shared connector is registered once here. Any assistant or Toolbox element in the organisation can then use it with **Use existing**, without its administrator ever handling the credentials.

## Adding one

**Add connector** opens a catalogue of known services you can search and filter by category. Picking one pre-fills most of the form. **Add a custom connector** configures one by hand.

The form is the same as for an assistant connector: name, server URL, transport and authentication. See [Connectors](/en/for-administrators/assistants/connectors.md) for the field-by-field detail.

One extra option appears here:

| Setting                          | What it does                                                       |
| -------------------------------- | ------------------------------------------------------------------ |
| **Share with sub-organizations** | Makes the connector available to your child organisations as well. |

{% hint style="warning" %}
Sharing with sub-organisations is fixed when the connector is created and cannot be changed afterwards. Decide before you save. To change it, create a new connector.
{% endhint %}

**Test connection** must succeed before you can save, and again after any change to the connection itself. From the test result you can already allow or block individual actions.

## Controlling actions centrally

**Manage actions** decides which of the server's actions are available. This is the main reason to share a connector: the decision is made once, by you, and every assistant inherits it.

Actions you block here are hidden everywhere and cannot be re-enabled by an assistant's own administrator. They see **Blocked by your organization** on the row.

Start with everything blocked except what is genuinely needed, particularly for connectors that can write, delete or send.

## Inherited connectors

A connector marked **Inherited** comes from a parent organisation. You can use it, but not edit it, delete it, or change which of its actions are allowed. The parent owns it.

One marked **Shared** is yours, shared downwards.

## Removing a connector

**Delete** removes it. If assistants or elements are still using it, you are warned and offered **Unlink and remove**, which disconnects them and deletes their stored credentials.

A connector still in use by a sub-organisation cannot be removed here at all. Those organisations must unlink it first.

{% hint style="danger" %}
Removing a shared connector breaks every assistant using it, at once. Check what depends on it first. The confirmation tells you how many.
{% endhint %}