# How analytics works

> How Overview and the Analytics tabs measure your team's work, who can see them, and how filters work.

**Overview** and **Analytics** in the sidebar show how your team ships code, and [Contribution](/contribution/) shows what devlo itself did. devlo.ai calls these pages Team Metrics. Only owners and admins can see them.

| Page                                 | What it answers                             |
| ------------------------------------ | ------------------------------------------- |
| [Overview](/analytics/overview/)     | How did the last 4 weeks go?                |
| [Throughput](/analytics/throughput/) | How much do we ship, and what kind of work? |
| [Quality](/analytics/quality/)       | What do reviews find?                       |
| [Delivery](/analytics/delivery/)     | Where do pull requests wait?                |
| [AI Usage](/analytics/ai-usage/)     | Where do our credits go?                    |

## Filters and data

The **Analytics** tabs filter by date range, member, and repository. Counting starts when devlo is installed, on connected repositories.

## Insights and badges

**Throughput**, **Quality**, and **Delivery** start with an **Insights** table that compares team members. Badges flag people who stand out from their peers; hover over a badge to see what it means.

Use person-level badges carefully

Most badges compare a person with peers in the range, ignoring the kind of work, seniority, and time off. Use them to start a conversation, not to rank people.

## Next steps

[Overview](/analytics/overview/)

[Throughput](/analytics/throughput/)

[Contribution](/contribution/)