> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/hub/chart-library.md).
# Chart Library
Common charts in Agentnoon and how to use them
Agentnoon provides a variety of charts to analyze your organization's structure, spans, layers, and costs.
## High-Level Organizational View Charts
These charts provide a **bird’s-eye view** of the organization:
* **Org Map** — Proportional split of headcount across the organization in one visual
* **Icicle Chart** — Abstract version of the org chart for navigation and summary insights
* **Proportion Chart** — Headcount distribution broken down across different areas of the company
## Span of Control Charts
Used to **analyze managerial spans**:
* **Span of Control Distribution** — Groups managers by span sizes (e.g., 1:1, 1:3, 3:5)
* **Average Span of Control** — Summary view of average span across departments or entities
## Layers & Hierarchy Charts
These charts help visualize **organizational depth and hierarchy**:
* **Headcount Heatmap** — Headcount distribution across levels, with department or entity on the x-axis
* **Layers & Span of Control Chart** — Combines layers and spans; x-axis = span, y-axis = department
* **Pyramid Chart** — Headcount distribution by layer or level; identifies whether the org is top-heavy, bottom-heavy, or balanced
## Cost Analysis Charts
Used to analyze **workforce expenses**:
* **Headcount Cost Chart** — Total cost by team or entity
* **Stacked Headcount Cost Chart** — Total cost broken down into components: salary, benefits, and additional expenses
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.agentnoon.com/hub/chart-library.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
