> For the complete documentation index, see [llms.txt](https://docs.trycaliber.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trycaliber.ai/using-caliber/for-team-leads.md).

# For team leads

What team leads see: scoped Home, briefing, peer comparisons, and coaching.

Team leads see Caliber scoped to their **starred team** (or a Shapes reporting subtree when that directory is connected). They can peer-browse other teams for aggregate comparisons without becoming org admins.

## Typical surfaces

* **Home** with a team lens (starred team vs whole-org when the product offers a toggle)
* **Team detail** for spend, adoption, and delivery signals
* **Lead briefing** board (coaching-oriented summary for the team)
* **Practitioners** list limited to the lead’s scope
* Peer aggregates on other teams (browse, not full org admin powers)

## What you cannot do

Connecting org-wide integrations, managing all members, and org-wide Code attribution admin remain **admin** powers. See [Roles and visibility](/getting-started/roles-and-visibility.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trycaliber.ai/using-caliber/for-team-leads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.