> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.11/development/flow-portal-2/getting-started.md).
# General
To the upper right in the portal the user name is displayed together with the options to go to the help, edit mode, quick start introduction and log out.
## Help
Click on the question mark icon to go to Flow Help.
## Administration mode
To make changes to the Portal setup (configurations, creating new portlets, etc.), go to edit view by clicking the *open settings* panel at the the top-right corner of the Portal.
Edit view requires user administration permission.
## Log in / log out
To access the Portal, start by logging in. Depending on the setup, users can login with either a Microsoft Account or a Flow account.
To log out of the Portal, use the drop down list available by the user name in the right-hand corner of the Portal and select *logout*.
### Quick start
Go to quick start to access the Portal introduction presentation.
---
# 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://help.novacuraflow.com/6.11/development/flow-portal-2/getting-started.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.
