> 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/command/the-portal.md).

# The Portal

- [The Portal](https://docs.ins-pi.com/command/the-portal/portal.md): Reference for the Command portal screen, covering Home, the top bar, the activity rail, tabs, the content header, the panels, the Command Dialog and Settings.
- [Content Types](https://docs.ins-pi.com/command/the-portal/content-types.md): Reference for every content type you can create in Command, with what each one is, when to use it and how to work with it.
- [Personas](https://docs.ins-pi.com/command/the-portal/personas.md): Reference for personas, the role-tailored workspaces that decide which content types and views each Command user is offered.
- [My Space and Sharing](https://docs.ins-pi.com/command/the-portal/my-space.md): Reference for My Space, where you save, organise, share, link, delete and restore your Command content.
- [Data Hub](https://docs.ins-pi.com/command/the-portal/data-hub.md): Reference for the Data Hub, the panel where you find ServiceNow records and drag them into your Command content.
- [Tasks, Notifications and Approvals](https://docs.ins-pi.com/command/the-portal/tasks-and-notifications.md): Reference for My Tasks, the notification bell and approvals, the places where Command asks you to act.


---

# 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/command/the-portal.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.