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

# Connectors

> Connect Velatir to an AI vendor's own administration API to bring in its activity, licences, and seats, with nothing to install on anyone's device.

## What Is a Connector?

A connector links Velatir to the administration API of an AI vendor your organisation already pays for. You approve the connection once, in the vendor's own admin tools. From then on Velatir reads what the vendor records about your organisation's use of it: conversations, licences, and how many seats are in use.

Nothing is installed on anyone's device, and nothing changes for the people using the service.

<CardGroup cols={2}>
  <Card title="Microsoft 365" icon="building-2" href="/connectors/microsoft-365">
    Microsoft 365 Copilot conversations, Copilot licences, and seats.
  </Card>
</CardGroup>

Microsoft 365 is the only connector today. More vendors will follow. [Claude Cowork](/connectors/claude-cowork) is set up the other way around: Cowork sends its activity to Velatir, so it does not appear in the connector list.

## Connectors and Device Capture

Connectors complement [Velatir for Desktop](/desktop-app/overview) and the [browser extension](/setup/browser-extension). They do not replace them.

| | Velatir for Desktop and the browser extension | A connector |
| - | - | - |
| **Where it sees activity** | On the devices where it is installed | Wherever the vendor records it, on any device |
| **When** | As the prompt is sent | After the fact, as the vendor makes its records available |
| **What else it brings** | Coaching, Redaction, and blocking at the moment of use | Licences and seat counts from the vendor |
| **Can it block a prompt** | Yes, with an agent in the Enforcer role | No. The interaction has already happened |
| **Setup** | Rolled out to devices | One approval by an administrator |

When both see the same conversation, Velatir reconciles them so it is not counted twice.

## What You Need

* The **Administrator** role in your Velatir organisation. Readers can see connections but cannot add, reconnect, or remove them. See [Roles & permissions](/platform/roles-and-permissions).
* An administrator account at the vendor, with the right to approve access for your whole organisation. Each connector's page says which role that is.

Approving a connection is always done by a person signed in to Velatir. An [API key](/api/overview) cannot approve one.

## Where Connectors Live

Connectors are part of the **Inventory**, the list of AI services your organisation declares it uses. Services are grouped by provider, and a provider that Velatir can connect to shows a **Connect** button on its card.

<Steps>
  <Step title="Declare a service from the provider" icon="clipboard-list">
    Open **Inventory** from the sidebar. If the provider is not listed yet, select **Declare service(s)** and declare one of its services. The provider's card then shows **Declared · not connected**.
  </Step>

  <Step title="Connect it" icon="plug">
    Select **Connect** on the provider's card and follow the steps. They differ per vendor, so follow the page for that connector.
  </Step>

  <Step title="Follow the connection on the card" icon="activity">
    The card gets a **Connections** section with the connection's status and, where the vendor reports them, its plans and seats.
  </Step>
</Steps>

A provider can hold more than one connection, for example one per Microsoft tenant. Select **Add connection** in the **Connections** section to add another.

<Note>
  If the card shows a lock and the message *Connecting vendors is not included in your plan*, connectors are not enabled for your organisation. Contact [hello@velatir.com](mailto:hello@velatir.com).
</Note>

## Connection Status

Each connection shows one status. Velatir works it out from the latest attempt to reach the vendor, so it is always current.

| Status | What it means | What to do |
| - | - | - |
| **Connected** | Velatir can read from the vendor. The caption says when it last synced, for example *Synced 5 minutes ago*. | Nothing. |
| **Action needed** | The vendor does not accept Velatir's access: the approval was never finished, was removed, or does not cover what Velatir needs. Velatir stops reading until it is fixed. | Read the alert on the card, then select **Reconnect**. |
| **Error** | The last attempt failed for a reason on the vendor's side, such as an outage. | Nothing. Velatir tries again on its own, and the last figures stay visible meanwhile. |

Velatir re-checks every connection's access every 15 minutes. If someone removes Velatir's access in the vendor's admin tools, the connection shows **Action needed** within that time.

## Activity From a Connector

Activity a connector brings in appears in **Sessions** like any other activity, dated when it happened rather than when Velatir read it. Its **Origin** is **Connector**, so you can filter for it, or leave it out.

* **Agents assess it after the fact.** Gatekeeper and Data Protector review connector activity as it arrives. The interaction has already happened, so an Enforcer's block is recorded but not enforced, and connector activity does not notify your [escalation channels](/traces/escalations).
* **Your privacy settings apply.** **Store trace data in sessions** decides whether the text of a connector conversation is kept, exactly as for every other session. The default is **Never**. See [Data privacy](/security/data-privacy).
* **Nothing is sent to the device.** Coaching and approval notices are not sent for connector activity. They need Velatir on the device at the moment of use.

## Reconnecting and Disconnecting

* **Reconnect** runs the vendor's approval again. The existing access stays in place until the new approval succeeds, and everything already imported is kept.
* **Disconnect** removes the connection and Velatir's access. Velatir can no longer read from the vendor for that connection. What it imported stays, and the declared services stay in the inventory. A provider with several connections offers **Disconnect all**, or you can remove one connection at a time.

Removing Velatir's access from the vendor's side has the same effect on access: the connection shows **Action needed**, and imported data is kept.

***

<CardGroup cols={2}>
  <Card title="Microsoft 365" icon="building-2" href="/connectors/microsoft-365">
    Connect a Microsoft 365 tenant.
  </Card>

  <Card title="Sessions and traces" icon="list" href="/traces/understanding-sessions">
    How activity is grouped once it reaches Velatir.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.