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

# Integrations

> Connect provider, seat, usage, spend, agent-platform, and telemetry data to Visibility.

Integrations add first-party data to Visibility. Availability is determined by workspace configuration, permissions, and the provider's own administrative requirements.

## Integration categories

<Tabs>
  <Tab title="Human AI tools">
    The shipped integration catalog includes Microsoft 365 Copilot, GitHub
    Copilot, Cursor, Codex / ChatGPT Enterprise, and Claude data paths. Depending
    on the provider, these can contribute seats, people, usage, spend, or
    interaction telemetry.
  </Tab>

  <Tab title="Agent platforms">
    The catalog includes read-only inventory paths for Copilot Studio, Azure AI
    Foundry, and Microsoft 365 declarative agents. The data available varies by
    platform and granted tenant permissions.
  </Tab>

  <Tab title="OpenTelemetry">
    Create a project and ingest key to receive OpenTelemetry traces from custom
    agent runtimes. Active keys and projects are managed from the integration
    settings.
  </Tab>
</Tabs>

## Connect a source

<Steps>
  <Step title="Choose the integration">
    Open **Settings → Integrations** and select an available provider.
  </Step>

  <Step title="Review the requested access">
    Confirm the tenant, organization, team, or workspace that will be connected
    and the permissions shown during setup.
  </Step>

  <Step title="Complete provider authorization">
    Follow the provider-specific OAuth, app installation, admin consent, API
    credential, or telemetry-key flow.
  </Step>

  <Step title="Verify status">
    Return to Integrations and confirm that the source reports connected. Some
    providers also show synced users, seats, organizations, agents, or projects.
  </Step>

  <Step title="Validate downstream data">
    Check the relevant People, Tools, Spend, Activity, or agent inventory view
    after the first successful sync or ingest.
  </Step>
</Steps>

<Info>
  A connected status confirms configuration, not that every downstream record
  is immediately available. Provider reporting windows and sync timing can
  affect when data appears.
</Info>