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

# Codebase Atlas

> See what your team merged, where it landed, who worked on it and what needs attention, without reading every merge request.

Codebase Atlas turns your merged pull requests (PRs) and merge requests (MRs) into a living map of your repository. Open it to see how the codebase is moving this week and which areas need a look.

## Why use Codebase Atlas

* **See the week on one screen.** Merged work, momentum and the kind of work, without opening each MR.
* **Know where changes land.** A CTO or team lead sees which parts of the product moved, and how much.
* **Spot what needs attention.** Open findings and quality show beside each area.
* **Understand the architecture.** The map shows components and how they use each other, which helps new engineers find their way.
* **Connect code to the business.** Atlas also maps your product's business flows, so Review can flag a change that breaks one. See [Business flow checks](https://docs.cloudthinker.io/guide/code-review/business-flow.md).

## Prerequisites

* A repository connected through [Review setup](https://docs.cloudthinker.io/guide/code-review/setup.md), with its setup finished.
* Review view permission to read an Atlas. Turning Atlas on or changing its branch needs Review edit permission; ask a workspace Admin if the controls are unavailable. See [roles](https://docs.cloudthinker.io/guide/security/roles.md).

## Turn on Atlas

**1. Open Codebase Atlas**

Click **Review** in the left navigation, then open **Codebase Atlas**. Select a repository from the picker at the top.

**2. Pick a branch and build**

In **Build your Codebase Atlas**, choose the **Branch** to follow. The default branch is selected for you. Click **Build Atlas**.

The page shows **Building your Codebase Atlas**. You can leave the page; the Atlas appears when it finishes.

**Success state:** the page shows your repository's Atlas and its merged changes.

Atlas then updates every day. The setup card shows the daily update time.

To turn Atlas on or off for many repositories, open **More actions → Manage repositories**. In the **Atlas branch** column, pick a branch for each repository, or pick **Off**. See [repository management](https://docs.cloudthinker.io/guide/code-review/repository-management.md).

## Read the week

Atlas opens on the **Review** view for the **Last 7 days**.

**1. Choose a period**

Open the period picker for **Last 7 days**, **Last 30 days** or **Custom range**. Use the previous and next arrows to step through periods.

**2. Read the period**

The first section sums up the period in three tiles:

| Tile | What it shows |
| - | - |
| **Momentum** | Merged changes compared with the same point last period |
| **Focus** | The areas that took most of the work |
| **Kind of work** | The split between **New**, **Fixed** and **Upkeep** |

Click **Analyze in Chat** to ask CloudThinker what advanced and what needs a decision.

**3. See where and who**

**Where and who** lists merges by area. Switch to **By person** to see each person's work across areas. Click **Open map** to see the same period on the map.

## Explore the map

**1. Open the map**

Choose **Map** in the view switcher, beside **Review** and **People**. The **Summary** cards above the map show **Merged MRs**, **Largest Impact share**, **Needs a look** and **Quality** for the period.

Use **Zoom in**, **Zoom out** and **Fit map to screen** to move around a large map.

**2. Open an area or component**

Click a group to expand it and see its components. Click a component to open its panel.

The **Overview** tab shows its numbers, the components it uses and is used by, and changes that need attention. The **Changes** tab lists every merged change in the period, with search.

**3. Open a change**

Select a change to see its Impact, Quality, summary and what changed. Click **Open review** to see its findings in the [Review workspace](https://docs.cloudthinker.io/guide/code-review/review-workspace.md).

**Success state:** you can trace an area of the map to the merged change behind it.

With nothing selected, the **Overview** panel shows the whole period. Click **Overview** at the top right to reopen it. Impact and Quality use the same scores as [Review Insights](https://docs.cloudthinker.io/guide/code-review/analytics.md).

From a component panel, **Copy changelog** copies the period's changes for that area, and **Open in Insights** opens [Review Insights](https://docs.cloudthinker.io/guide/code-review/analytics.md).

To share what you see, open **More actions → Copy link**. The link keeps the repository, period and selected component.

## Explore people

Choose **People** in the view switcher to see who changed which areas in the period. Select a person or a cell to open their changes. A component panel also has a **People** tab with its contributors.

Use it to find who knows an area, or where one person's work landed. It shows contribution, not performance. Bot changes are counted separately.

## How it works

1. **Map.** CloudThinker reads the branch you chose and draws its components.
2. **Place.** Each merged change lands on the component it touched.
3. **Score.** Each change carries its Review Impact, Quality and open findings.
4. **Update.** Atlas refreshes every day.

## Troubleshooting

> [accordion] No merges in the selected period
>
> **Cause:** nothing merged into the Atlas branch in that period. The map stays visible.
>
> **Fix:** click **View** with the dates of the last merge, or choose a longer period such as **Last 30 days**.

> [accordion] Building your Atlas
>
> **Cause:** the first build or a daily update has not finished.
>
> **Fix:** wait, or leave the page and come back. If the page stops updating, click **Refresh** when it is offered.

> [accordion] Your assessment needs another try
>
> **Cause:** the first build did not finish. The page names the reason, for example **Branch unavailable** or **Took too long**.
>
> **Fix:** check the repository connection and the branch, then click **Retry assessment**. Your repository and branch choice are saved.

> [accordion] The Atlas branch no longer exists
>
> **Cause:** the branch was renamed or deleted.
>
> **Fix:** open **More actions → Manage repositories** and pick another branch in the **Atlas branch** column.

> [accordion] Connect a repository first
>
> **Cause:** no repository has finished Review setup.
>
> **Fix:** click **Review settings** and finish or retry setup for the repository.

> [accordion] Ask an admin to build the Atlas
>
> **Cause:** your role can view Review but cannot edit it.
>
> **Fix:** ask a workspace Admin to build the Atlas or update your role.

## Related

> [card] [Repository management](https://docs.cloudthinker.io/guide/code-review/repository-management.md)
>
> Choose the Atlas branch for each repository, or turn Atlas off.

> [card] [Review Insights](https://docs.cloudthinker.io/guide/code-review/analytics.md)
>
> Track review quality and contribution trends across the team.

> [card] [Review workspace](https://docs.cloudthinker.io/guide/code-review/review-workspace.md)
>
> Inspect the findings and status of an individual change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.