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

# Quickstart

> Get up and running with Navigara's cloud platform in minutes.

<Info>This guide covers the cloud SaaS version. For self-hosted options, see [Deployment](/deployment/overview).</Info>

## 1. Sign up

Create your account at [app.navigara.com](https://app.navigara.com) using email, Google, or GitHub authentication.

## 2. Create an organization

After signing in, create your organization. This is the top-level container for all your repositories, teams, and settings.

## 3. Connect your Git provider

Navigate to **Settings → Connections**. Everything Navigara reads from lives on this one page, grouped into **Source control** and **Task tracking**. Under **Source control**, click **Add connection** and pick your provider:

* **GitHub** — install the Navigara GitHub App (or paste a personal access token)
* **GitLab** — OAuth, or a personal/group access token
* **Bitbucket** — workspace access token or app password
* **Azure DevOps** — Microsoft Entra ID OAuth, or a personal access token

Read-only access is sufficient for every provider. See [Integrations](/integrations/overview#git-providers) for required scopes.

## 4. Connect task management (optional)

Task tracking powers **Alignment** scoring by correlating commits and PRs with the work items they deliver. Under the **Task tracking** section of the same **Settings → Connections** page, click **Add connection** and pick a provider:

* **Linear** — authorize via OAuth, or paste a personal API key
* **Jira Cloud** — authorize with your Atlassian account, or provide a site URL + API token
* **Jira (Server / Data Center)** — base URL + personal access token
* **Asana** — personal access token

After the credentials are validated, a short **setup wizard** opens so you can:

1. **Choose scope** — sync all teams/projects in the workspace, or just a selected subset.
2. **Map issue types** — place each issue type on the alignment ladder: **Objective**, **Sub-objective**, **Issue**, or **Ignored**. Suggestions are pre-filled, and you can re-open the wizard anytime to adjust scope or mappings.

Saving the wizard for the first time kicks off the initial sync.

## 5. Track AI coding tool usage (optional)

See how your team actually uses AI assistants — cost, tokens, models, and which developers are active — on the **Tool Spend** dashboard. Under the **AI tools** section of the same **Settings → Connections** page, pick a tool and click **Generate token & config**: Navigara mints a write-only ingest token and hands you a ready-to-copy config that ships usage telemetry over OpenTelemetry (OTLP). You control what leaves the workstation — by default only usage metadata (cost, tokens, models, durations, tool names), with per-tool flags to opt into prompt and tool content.

<Info>
  **Any plan or license works — we support them all.** Ingestion is pure OpenTelemetry, independent of how you pay for the tool. There's nothing to buy or upgrade to be measured.
</Info>

The complete examples below use the cloud endpoint `https://app.navigara.com/api/otlp`; self-hosted deployments substitute their own host. See [AI Coding Tools](/integrations/ai-tools) for the full reference.

<AccordionGroup>
  <Accordion title="Claude Code" icon="robot">
    Claude Code has native OpenTelemetry support. Add to a developer's shell profile (or ship the equivalent `env` block via MDM managed settings for a whole fleet):

    ```bash theme={null}
    export CLAUDE_CODE_ENABLE_TELEMETRY="1"
    export OTEL_METRICS_EXPORTER="otlp"
    export OTEL_LOGS_EXPORTER="otlp"
    export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
    export OTEL_EXPORTER_OTLP_ENDPOINT="https://app.navigara.com/api/otlp"
    export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <YOUR_INGEST_TOKEN>"
    ```

    On Claude.ai (Team / Enterprise) sign-in, the developer's email is emitted natively. Under API-key / Bedrock / Vertex auth, also set `OTEL_RESOURCE_ATTRIBUTES="enduser.id=$(git config user.email)"` so usage is attributed to the right person.
  </Accordion>

  <Accordion title="GitHub Copilot" icon="github">
    Copilot CLI telemetry is off by default and is configured through environment variables. Add to a shared profile (e.g. `/etc/profile.d/`) or a `copilot` launcher wrapper:

    ```bash theme={null}
    export COPILOT_OTEL_ENABLED="true"
    export OTEL_EXPORTER_OTLP_ENDPOINT="https://app.navigara.com/api/otlp"
    export OTEL_EXPORTER_OTLP_PROTOCOL="http/json"
    export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <YOUR_INGEST_TOKEN>"

    # Copilot emits no identity — enduser.id is how usage is attributed, matched by email.
    export OTEL_RESOURCE_ATTRIBUTES="enduser.id=$(git config user.email)"
    ```
  </Accordion>

  <Accordion title="OpenAI Codex" icon="code">
    Codex configures OTLP through `~/.codex/config.toml` (telemetry off by default):

    ```toml theme={null}
    # ~/.codex/config.toml
    [otel.metrics_exporter.otlp-http]
    endpoint = "https://app.navigara.com/api/otlp/v1/metrics"
    protocol = "binary"
    headers = { Authorization = "Bearer <YOUR_INGEST_TOKEN>" }

    [otel.exporter.otlp-http]
    endpoint = "https://app.navigara.com/api/otlp/v1/logs"
    protocol = "binary"
    headers = { Authorization = "Bearer <YOUR_INGEST_TOKEN>" }
    ```

    Codex metrics carry no identity, so set it per workstation in the shell profile:

    ```bash theme={null}
    export OTEL_RESOURCE_ATTRIBUTES="enduser.id=$(git config user.email)"
    ```
  </Accordion>

  <Accordion title="LiteLLM" icon="network-wired">
    Run one proxy in front of your providers and capture usage for everything routed through it. Requires LiteLLM ≥ 1.89.

    Enable the OTel callback in `config.yaml`:

    ```yaml theme={null}
    litellm_settings:
      callbacks: ["otel"]
    ```

    Then set on the proxy deployment:

    ```bash theme={null}
    export LITELLM_OTEL_INTEGRATION_ENABLE_METRICS="true"
    export OTEL_EXPORTER="otlp_http"
    export OTEL_EXPORTER_OTLP_ENDPOINT="https://app.navigara.com/api/otlp"
    export OTEL_HEADERS="Authorization=Bearer <YOUR_INGEST_TOKEN>"
    ```

    Attribute usage to developers with per-user virtual keys, JWT/OIDC SSO, or the OpenAI-compatible `user` request field — see [AI Coding Tools → LiteLLM](/integrations/ai-tools#litellm).
  </Accordion>
</AccordionGroup>

## 6. Add your first repository

Go to **Repositories > Add Repository**, select your connected provider, and choose the repository to analyze. Navigara will begin processing commits automatically.

## 7. View results

Once analysis completes, explore the dashboard to see:

* **Performance scores** for individual contributors
* **Alignment scores** correlating commits with tasks
* **AI-powered commit summaries** and knowledge graphs