> For the complete documentation index, see [llms.txt](https://docs.icepanel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icepanel.io/core-features/diagramming/diagrams-section.md).

# Diagrams section

The diagrams section contains a list of all your diagrams in the landscape or domain.  Use this section to find specific diagrams, create a new context diagram, view essential insights, and manage diagrams.

<figure><img src="/files/gmRRoPRfGa3znH63TEBv" alt=""><figcaption><p>Diagrams section</p></figcaption></figure>

In the diagrams section, you can:

* Create a context diagram
* Search for diagrams
* Sort diagrams by any column (name, domain, C4 level, contributors, last edit, views, edits) over specific periods (today, yesterday, this week, this month, all time)
* Perform diagram actions
  * Add a diagram to a group
  * Duplicate (admin or editors only)
  * Move the diagram to another domain/system/app (admin or editors only)
  * Pin or unpin the diagram (admin or editors only)
  * Delete the diagram (admin or editors only)


---

# 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.icepanel.io/core-features/diagramming/diagrams-section.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.