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

# Quickstart

> Set up Velatir and start monitoring AI usage across your organisation.

This guide takes you from a new account to your first assessments. It should take about fifteen minutes.

## Before You Start

You need an organisation in Velatir and administrator access to it. If you are signing up for the first time, the onboarding wizard walks you through creating your organisation and your first workspaces.

<Tip>
  When you create your organisation you can name workspaces yourself, or generate them automatically from your directory with Microsoft Entra. See [Microsoft Entra](/platform/microsoft-entra) to decide which fits your organisation.
</Tip>

## Set Up Monitoring

<Steps>
  <Step title="Choose how you connect" icon="plug">
    Open **Setup** in the dashboard. Most teams install **[Velatir for Desktop](/desktop-app/overview)**, one installer that covers AI use in the browser and in desktop apps. If you only need browser coverage, deploy the [browser extension](/setup/browser-extension) on its own.
  </Step>

  <Step title="Generate an API key" icon="key-round">
    On the Setup page, generate an API key. Copy it straight away, as it is shown only once. You can manage keys later under **Settings → API keys**.
  </Step>

  <Step title="Deploy to your team" icon="users-round">
    Roll **Velatir for Desktop** out to your fleet with your ingest key. [Enterprise deployment](/desktop-app/enterprise-deployment) covers silent installation via Microsoft Intune, Jamf Pro, and other MDM platforms across Windows and macOS.
  </Step>

  <Step title="Watch activity arrive" icon="activity">
    As people use AI, sessions and traces appear under **Sessions**, and agent verdicts appear under **Agents → Assessments**.
  </Step>

  <Step title="Tune your agents" icon="sliders-horizontal">
    Open **Agents** to set how each one behaves. Start in Observer to learn your usage, then move to Enforcer where it matters. See [Configuring agents](/agents/configuring-agents).
  </Step>
</Steps>

## Recommended First Week

<AccordionGroup>
  <Accordion title="Run in Observer first" icon="eye">
    Keep both agents in Observer for the first week or two. You build a clear picture of what people use and what would be flagged, with no disruption.
  </Accordion>

  <Accordion title="Review what was flagged" icon="list-checks">
    Check **Agents → Assessments** to see what each agent caught. This tells you which services to allow or block and which data categories matter most.
  </Accordion>

  <Accordion title="Set your service policy" icon="shield-check">
    Use [Gatekeeper](/agents/gatekeeper) to decide which AI services are allowed, and [Data Protector](/agents/data-protector) to decide which sensitive content to catch.
  </Accordion>

  <Accordion title="Connect a channel" icon="bell">
    Add a channel under **Settings → Channels** so escalations reach the right people in Slack, Microsoft Teams, or by phone.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Core concepts" icon="lightbulb" href="/core-concepts">
    Understand organisations, agents, traces, and instructions.
  </Card>

  <Card title="Configuring agents" icon="sliders-horizontal" href="/agents/configuring-agents">
    Roll agents out from Observer to Enforcer.
  </Card>
</CardGroup>