> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/models/work-in-the-app/editor/shape-libraries.md).
# Shape Libraries
YouDesign Models ships with a broad set of **shape libraries** organized into categories. Each library is a curated set of shapes designed for a specific use case — architecture, cloud, process modeling, annotation, and more. New libraries are added with every release.
This page is a reference for what's bundled. For how to add a single shape to a board, see [Shapes](/models/work-in-the-app/editor/shapes.md).
## Where to Find the Libraries
Open the **Diagramming** panel in the left sidebar of the editor. Libraries are listed as expandable categories. Use the search box at the top of the panel to search across all libraries at once.
> 
## Core Libraries
| Library | Description |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Basic Shapes** | Fundamental geometric shapes — circles, squares, triangles, rectangles — plus **Lane** and **Task** for boards and **Entity Table** / **Entity Field** for ERD diagrams (see [Entity Tables](/models/work-in-the-app/editor/entity-tables.md)). |
| **Arrows** | Arrow shapes for indicating direction, flow, or relationships — useful in flowcharts and process maps. |
| **Notes** | Annotation shapes (sticky notes, callouts) for comments or explanations alongside diagram content. |
| **Logos** | Predefined logos for branding, presentations, or representing specific companies, technologies, or software. |
## Architecture & Framework Libraries
| Library | Description |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Archimate** | Official Opengroup Archimate shape library. Available on request — contact your ins-pi representative to have it installed. |
| **C4** | Shapes based on the C4 model for software architecture (Person, System, Container, Component). |
| **Architecture** | Shapes and symbols used in enterprise architectural planning and design. Inspired by the ins-pi UPMX methodology. |
| **Metamodel** | Shapes for documenting data metamodels — entities, attributes, cardinalities. |
| **BPMN** | Business Process Model and Notation: events, activities, gateways, artifacts, data objects, pools and lanes, and around 20 sub-process shapes that expand and collapse. See [BPMN Shapes & Swimlanes](/models/bpm-process/bpmn-shapes.md). |
## Cloud Platform Libraries
| Library | Description |
| --------- | --------------------------------------------------------------------------------- |
| **AWS** | Official AWS Architecture icon set for building AWS architecture diagrams. |
| **Azure** | Official Azure Public Services icon set for building Azure architecture diagrams. |
| **GCP** | Google Cloud Platform official icons. |
## ServiceNow & Infrastructure Libraries
| Library | Description |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **ServiceNow** | Specific to the ServiceNow platform — shapes for the Common Services Data Model (CSDM) and other modules (GRC, ITSM, etc.). |
| **Designer Network** | Network-diagramming shapes ported from the legacy ins-pi Designer application — servers, routers, switches, workstations. |
## Requesting a Library
If your team needs a library that isn't bundled, contact your **ins-pi representative**. Custom and community libraries can be installed into your YouDesign Models instance without waiting for a platform release.
Custom shape development (entirely new shape sets with your brand or a proprietary methodology) is also available as a professional service — see the [Support Process](/models/reference/support.md).
## Admin Configuration
Administrators can extend or modify libraries directly. See:
* [Shape Administration](/models/admin/shapes.md) — adding and editing individual shapes
* [Shape Categories](/models/admin/shapes.md#shape-categories) — creating and reorganizing categories
Changes to libraries migrate via [XML export/import](/models/get-the-app/migrating-configuration.md), not via Update Sets.
## Related
* [Shapes](/models/work-in-the-app/editor/shapes.md) — adding, moving, and styling individual shapes
* [Text Formatting](/models/work-in-the-app/editor/text-formatting.md) — styling text within shapes
* [Favorites](/models/work-in-the-app/editor/favorites.md) — save your most-used shapes for one-click access
* [Shape Administration (admin)](/models/admin/shapes.md) — configuring shapes and categories
---
# 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.ins-pi.com/models/work-in-the-app/editor/shape-libraries.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.