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

# Data & Analytics

> Teams analytics: dashboard metrics, permissions, and how AI share of commits is calculated.

<Info>
  Applicable plans: Teams, Enterprise
</Info>

This article explains Qoder Teams **data metrics**: what each dashboard shows, how figures are defined, who can see what, and how **AI share of committed code** is **calculated and attributed in the product**.

## Dashboard metrics

### AI share of committed code

<img src="https://mintcdn.com/qoder/V0zN5TAiiuDl2IXR/images/teams-analytics-ai-share.png?fit=max&auto=format&n=V0zN5TAiiuDl2IXR&q=85&s=efd79adabe9b9757f40c78bedcdcfbe0" alt="AI share of committed code" width="1024" height="522" data-path="images/teams-analytics-ai-share.png" />

**Definition:** Among lines in commits, the proportion generated with AI. **AI** here includes **Agent**, **Edit**, and **NEXT**.

**Filters:**

* Filter by **repository** (derived from Git metadata).
* Option to **main branch only**.

**Reading the numbers:** If your team also authors code with **third-party tools** alongside Qoder, total lines per commit often include that output. That output is **not** counted in the dashboard’s AI-generated **numerator**, but may still contribute to the **denominator**, so the **share shown on the page can look lower than expected**. Treat the in-product dashboard as the source of truth.

### Agent retained lines

<img src="https://mintcdn.com/qoder/V0zN5TAiiuDl2IXR/images/teams-analytics-agent-lines.png?fit=max&auto=format&n=V0zN5TAiiuDl2IXR&q=85&s=313dc2a1e06e518fb68958ec1217a2df" alt="Agent retained lines" width="1024" height="526" data-path="images/teams-analytics-agent-lines.png" />

**Definition:** Lines from **Agent** and **Edit** that remain in the repository, including added and removed lines attributed to Agent.

You can break this down by **file extension**. Extensions are grouped as follows:

* **Front end:** `.js`, `.jsx`, `.ts`, `.tsx`, `.vue`, `.svelte`, `.html`, `.css`, `.scss`, `.less`, `.sass`
* **Back end:** `.py`, `.java`, `.go`, `.rs`, `.rb`, `.php`, `.cs`, `.kt`, `.scala`, `.swift`, `.m`
* **Systems / low-level:** `.c`, `.cpp`, `.h`, `.hpp`, `.asm`
* **Scripts / config:** `.sh`, `.bash`, `.zsh`, `.ps1`, `.bat`, `.yaml`, `.yml`, `.toml`, `.json`, `.xml`, `.ini`, `.env`
* **Data / query:** `.sql`, `.graphql`, `.prisma`
* **Mobile:** `.dart`, `.swift`, `.kt`
* **Docs / markup:** `.md`, `.mdx`, `.rst`, `.tex`
* **Other:** `.r`, `.lua`, `.perl`, `.ex`, `.exs`, `.clj`, `.hs`, `.erl`, `.zig`, `.nim`, `.proto`, `.tf`, `.dockerfile`

### NEXT acceptances and recommendations

<img src="https://mintcdn.com/qoder/V0zN5TAiiuDl2IXR/images/teams-analytics-next.png?fit=max&auto=format&n=V0zN5TAiiuDl2IXR&q=85&s=c5e468b1b96eb8e4243fa739a230b236" alt="NEXT acceptances and recommendations" width="1024" height="525" data-path="images/teams-analytics-next.png" />

* **NEXT acceptances:** Total accepted NEXT completions.
* **NEXT recommendations:** Total NEXT suggestions shown.

## Permissions

Data metrics are available to members of organizations where the capability is enabled. **Role controls scope**:

| Role       | Access                     |
| ---------- | -------------------------- |
| **Admin**  | Organization-wide metrics. |
| **Member** | **Own** metrics only.      |

**Members** can use data metrics and view reports tied to their own activity. **Admins** can additionally view organization-wide rollups and member-level views **when the product UI provides them**. Effective scope depends on organization settings and the current product version.

## AI share of committed code: rules and attribution

The table below describes which kinds of commits are included or filtered under the current policy. **Applied** means the rule **participates** in filtering or counting for this metric.

| Rule                         | Description                                                                                                                                                                                | Applied |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------- |
| **Huge commit filter**       | Typical of bulk dependency imports, migrations, vendor drops, and similar non-hand-authored changes; **abnormally large** single commits may be detected and **excluded** from this metric | Yes     |
| **Merge-only / local merge** | Commits that mainly reflect pull/merge/sync **without substantive code changes** are generally excluded from this metric                                                                   | Yes     |
| **Revert commits**           | Rollbacks of earlier commits; **not excluded under the current policy**                                                                                                                    | No      |
| **Squash / amend**           | In **some workflows or toolchains**, the same change set **may be counted more than once**                                                                                                 | Yes     |
| **Bulk format-only commits** | Pure formatting from **common code formatters**; **not excluded under the current policy**, to stay consistent with post-processed code states                                             | No      |

**Note:** Whether Squash/Amend causes duplicate counting depends on workflow and tooling; **use the in-product dashboard as the final reference**.

**Attribution and boundaries (product behavior tied to how you commit):**

* **Sync-style merges:** Changes that are merges from a remote into a local checkout **without substantive code edits** are **not** included in the basis used for this metric’s AI attribution (aligned with **Merge-only / local merge** above).
* **Renames and copies:** If you only **rename paths** after generation, or **copy** generated content to a new path and commit there, the new path usually **cannot** be attributed to Qoder AI under the rules, so those changes **do not** count toward this metric’s AI-generated tally.
* **Multiple directories / worktrees:** If checkout paths change often (multiple working directories, worktrees, etc.), changes **can still count** when they remain attributable to generation under the product rules.
* **Amend and follow-up commits:** After **amend** or similar rewrites, lines that are still **Qoder AI–generated** **continue to count** as AI-generated.
* **Very large dependency or artifact files:** Accidentally committing huge `.module`-style artifacts usually falls under **abnormally large** commit handling; such commits may be **excluded wholesale** from the basis of this metric—**see the dashboard**.