> 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/work-in-the-app/user-interface/access-designer.md). # Access Designer Description of how to access Designer's features via the ServiceNow app navigator. The Designer Application menu is structured as follows: ![Designer menu](https://2424003387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRt6kkrmmoQeRFJQUp63x%2Fuploads%2Fgit-blob-77ae47cf85fe5d889d9b8c01ac1914b8a77f5ff7%2F2e235df-Designer_Menu.png?alt=media) | Menu Entry | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Designer | The main Designer Canvas for modeling & diagraming | | Diagrams | Overview of all Diagrams | | Class Definitions | *Visible for Designer Admins only.* | | Filters | Configuration of Global Filters *Visible for Designer Admins only.* | | Realtime Indicators | Configuration of Realtime indicators *Visible for Designer Admins only.* | | Relationship Definitions | Configuration of Relationship Definitions and Relationship Fields *Visible for Designer Admins only.* | | Shape Libraries | *Visible for Designer Admins only.* | | Templates | Template table to set Global Templates *Visible for Designer Admins only.* | | License Management Dashboard | Dashboard to see the balance between available and used licenses. \[see further information here] *Visible for Designer Admins only.* | | Contact Support | Refers you to the ins-pi support team to request 3rd level support or a new feature. | | User Guide | Links you to the Designer Knowledge Base | The visibility of different menu items is based on Roles and access control (ACL) rights. --- # 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/work-in-the-app/user-interface/access-designer.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.