> ## 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.

# Visibility

> Understand AI adoption, activity, spend, tools, and governance across your organization.

Visibility shows what AI your company actually runs on: the tools, accounts, models, people, agents, workflows, and spend spread across the organization.

It is not a static SaaS inventory or a one-time audit. Visibility brings together identity, activity, license, billing, integration, and endpoint signals so teams can understand how AI is being used and decide what to fund, standardize, review, or restrict.

<Info>
  The pages and data available to you depend on your workspace configuration,
  role, and data scope.
</Info>

<Card title="Start with one complete investigation" icon="rocket" href="/docs/visibility/quickstart">
  Verify the data foundation, establish a baseline, follow one signal, and turn
  the evidence into a concrete next action.
</Card>

## Explore Visibility

<Columns cols={2}>
  <Card title="Adoption overview" icon="chart-line" href="/docs/visibility/adoption">
    Track engagement, active people, tools, use cases, and changes over time.
  </Card>

  <Card title="People, departments, and tools" icon="users" href="/docs/visibility/people-departments-tools">
    Move from organization-wide trends to the people, teams, and products behind them.
  </Card>

  <Card title="Workflows and cohorts" icon="workflow" href="/docs/visibility/workflows-cohorts">
    Find recurring work patterns and groups with similar adoption behavior.
  </Card>

  <Card title="Spend" icon="wallet-cards" href="/docs/visibility/spend">
    Reconcile contracted, unapproved, and recoverable AI spend.
  </Card>

  <Card title="Activity review" icon="activity" href="/docs/visibility/activity-review">
    Review captured conversations and coding sessions with scoped filters.
  </Card>

  <Card title="Tool governance" icon="shield-check" href="/docs/visibility/tool-governance">
    Review tools, access requests, policies, and policy detections.
  </Card>
</Columns>

## Build the data foundation

<Columns cols={2}>
  <Card title="Integrations" icon="plug" href="/docs/visibility/integrations">
    Connect supported provider, seat, usage, spend, and telemetry sources.
  </Card>

  <Card title="Endpoint agent" icon="monitor-cog" href="/docs/visibility/endpoint-agent">
    Understand the managed endpoint collection and control plane.
  </Card>

  <Card title="Browser extension and collector" icon="panel-top" href="/docs/visibility/browser-extension-collector">
    Compare browser activity capture with local coding and agent collection.
  </Card>

  <Card title="Devices, deployment, and privacy" icon="laptop-minimal-check" href="/docs/visibility/devices-deployment-privacy">
    Plan rollout, monitor device health, and apply workspace data controls.
  </Card>
</Columns>

## What Visibility helps answer

* Which AI tools are being used, by whom, and in which departments?
* Which workflows repeat, and where is adoption concentrated or stalled?
* Which paid seats are active, idle, duplicated, or outside approved contracts?
* Which tools and access requests need an administrative decision?
* Which collection paths are contributing data, and which devices need attention?

## A connected operating loop

Visibility connects observation to action:

<Steps>
  <Step title="Collect">
    Bring in provider integrations, managed endpoint signals, browser activity,
    local collector data, or model traffic configured for your workspace.
  </Step>

  <Step title="Resolve">
    Associate activity with people, departments, accounts, tools, and devices.
  </Step>

  <Step title="Understand">
    Compare adoption, workflows, activity, and spend across the scope available
    to your role.
  </Step>

  <Step title="Act">
    Review tools, respond to access requests, adjust policies, reclaim spend,
    and improve deployment coverage.
  </Step>
</Steps>

<Card title="Review the data-source architecture" icon="database" href="/docs/platform/data-sources">
  See how endpoint, browser, local, integration, and model-traffic data fit together.
</Card>
