> 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/development/flow-portal-2.md). # Portal 2 Novacura Flow Portal is about making relevant information, actions and tools available for any person who needs it in any type of situation. With powerful tools for visualization and workflows as a foundation for actions and data, the possibilities are endless. Novacura Flow Portal is about making relevant information, actions and tools available for any person who needs it in any type of situation. With powerful tools for visualization and workflows as a foundation for actions and data, the possibilities are endless. Flow Portal 2 takes everything one step further. The flexible [navigation](/development/flow-portal-2/getting-started/navigation.md) makes it possible to create virtually any type of portal, of any size. Various layout options make it possible to display whatever information you want on your [page](/development/flow-portal-2/getting-started/add-pages-and-portlets.md), exactly how you want to display it. Combine that with an improved user experience and you'll see that Flow Portal 2 is an excellent tool to enable business improvement for any type of situation. Flow Portal 2 can be used to visualize and manage all types of processes, including: * manufacturing planning and execution * Lean/Agile boards, continuous improvement and collaboration * customer portals * supplier portals * work order planning, dispatching and execution * warehouse control ...and a whole lot more. ![Flow Portal Production Monitoring.](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M0sLhwoqCSJPxswhB7l%2F-M0sRdiJ48_ua9IyJvhX%2FScreenshot%202020-02-24%20at%2019.19.32.png?alt=media\&token=0af2ee7c-ddfc-42f0-a9e1-e55c40d72cd6) ![Work Order Control and Execution.](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M0sLhwoqCSJPxswhB7l%2F-M0sS3jZiveyvQN4IXw0%2FScreenshot%202020-02-24%20at%2019.14.03.png?alt=media\&token=be3434b0-cf49-4aee-9bf3-7ea548d3b96a) --- # 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/development/flow-portal-2.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.