> 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/designer/designer-reader/overview.md).

# Overview

Designer is a real-time Diagraming and Modeling application natively running on the ServiceNow platform. To find out more about Designer, visit our [About Designer](https://github.com/ins-pi-GmbH/designer-app/blob/v5.9.3/Documentation/designer-reader/about-designer.md) page.

This section is dedicated to users with the 'Designer Reader' role. This role is the 'read-only' role in Designer.

Users with this role have access to the diagram list and can open all diagrams that are shared with them in presentation mode.

They can access the diagrams either through the Designer diagram form or direct link to the diagram. To see the list of available diagrams, open your ServiceNow instance and enter 'Designer' in the application navigator and select 'Diagrams' as shown in B in below image.

The application menu available to Designer readers:

**A** - Opens the [Diagram Form](/designer/designer-reader/diagram-form.md) form in a new browser tab **B** - Open the Designer Knowledge Base (this documentation site)


---

# 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/designer/designer-reader/overview.md?ask=<question>&goal=<user_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.