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

# Team insights in Base Code

> See how your team delivers code from its GitHub history in Base Code Insights, from who works on what to where pull requests wait and how much of it AI writes.

Insights turns your team's GitHub history into numbers you can act on, so you can spot where work slows down and decide what to change. It opens from **Insights** in the Base Code sidebar.

***

## Using Insights

Track your team's pull requests across your GitHub repos, and keep the numbers accurate.

### Viewing Insights

See how your team delivers code, from who works on what to where pull requests wait and how much of the work AI writes. Insights is built from your GitHub history and updates every night, so your numbers appear after the first nightly update.

Insights has 2 views:

* **Team:** Your team's numbers, from quick takeaways to where pull requests wait.
* **You:** Your own numbers next to your team's, including your Base Code pull requests. Only you can see it, and its comparisons show when at least 5 people work in the selected repos.

> [!NOTE]
>
> Everyone in your workspace can see who's in each work group. If you're a workspace owner or admin, you also see who's working on each part of the code under **In flight**.

The **Team** view includes:

| Section | What it shows |
| - | - |
| **Quick insights** | The main takeaways, each with a link to the section it comes from. |
| Numbers at the top | Merged pull requests, active developers, review and merge times, and the share co-authored with AI. |
| **Merged PRs per week** | Every merged pull request each week, colored by the AI agent that co-authored it. |
| **Base Code** | How Base Code's pull requests compare with the rest, and which ones needed the most fixing. |
| **Work groups** | Who works on what, and the parts of the code each group changed most in the last 14 days. |
| **In flight** | The parts of the code with the most merged work in the last 14 days. |
| **Where work waits** | Review and merge waits, who approves, pull request size, and findings from review bots. |
| **Code flow** | Lines added and deleted. |
| **Merge clock** | The hours of the day when pull requests merge. |

**To view Insights:**

1. Go to [Base Code](https://app.base44.com/base-code).
2. Click **Insights** in the sidebar.
3. (Optional) Choose what to see:
   * **Whose numbers:** Click **Team** for your team's numbers, or **You** for your own.
   * **Which repos:** Open the repo menu at the top of the page and select **All repos** or one repo.
   * **Which dates:** In one repo or the **You** view, select a range, such as **Last 30 days**, or **Custom range…** for up to 2 years. With **All repos** in the **Team** view, Insights shows the last 90 days.

### Managing Insights

Choose which repos Insights counts and keep your work groups up to date, so your team's numbers match how you work.

> [!WARNING]
>
> You need to be a workspace owner or admin to choose repos and edit work groups.

#### Choosing repos

Choose which repos count toward your team's numbers, for example to add a repo Insights left out.

**To choose repos:**

1. Go to [Base Code](https://app.base44.com/base-code).
2. Click **Insights** in the sidebar.
3. Open the repo menu at the top of the page and select **Manage repos…**.
4. Select each repo you want Insights to count, and clear the ones you don't. Repos under **Not counted** were left out because they look personal or test-only.
5. Click **Save**. Insights picks up your changes at the next hourly update, and a repo you added shows its numbers after the next nightly update.

#### Editing work groups

Insights groups people by who works together on merged pull requests. If a group doesn't match how your team works, edit it.

**To edit a work group:**

1. Go to [Base Code](https://app.base44.com/base-code).
2. Click **Insights** in the sidebar.
3. Click a group under **Work groups**.
4. Choose what to change:
   * **Rename the group:** Click **Rename group**, enter a name, then click **Save name**.
   * **Move a person:** Select another group in **Move to…** next to their name.
   * **Confirm the group:** Turn **Confirmed** on or off. When it's on, nightly updates suggest membership changes instead of applying them.
   * **Merge the group:** Choose a group under **Merge into another group**, then click **Merge groups**. This group's people join the other group, and this group is removed. The other group becomes confirmed.

***

## FAQs

> [accordion] Why does a repo show Can't reach GitHub in Insights?
>
> Insights reads each repo through the GitHub connection of the person who added it, and that connection has stopped working. If you added the repo, [connect your GitHub account](https://docs.base44.com/base-code/getting-started.md#connecting-your-github-account) again. Otherwise, ask the person who added it to reconnect, or ask a workspace owner or admin to check your [GitHub organizations](https://docs.base44.com/base-code/getting-started.md#managing-github-organizations).
>
> Insights picks the repo up within the hour, and its numbers return after the next nightly update.


## Related topics

- [Managing branches and pull requests in Base Code](https://docs.base44.com/base-code/branches-and-pull-requests.md)
- [Getting started with Base Code](https://docs.base44.com/base-code/getting-started.md)
- [Making changes in Base Code](https://docs.base44.com/base-code/making-changes.md)
- [Base44 developer tools](https://docs.base44.com/documentation/building-your-app/developer-tools.md)
- [Code Tab](https://docs.base44.com/developers/app-code/editor/code-tab.md)


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