> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/portal-pages/create-portal-page.md).

# Create Portal Page

A portal page is the item that will be visible to the End user in the navigator. It is the area where portlets are added and configured. You create, delete and edit metadata for pages in the Hub. The application logic is then developed in the Flow Portal.

## Create page

* Select the application package to open the package content view.
* Select **New** and then **Portal Page**.

<figure><img src="/files/le5DpnibznxxCMlSEQI9" alt=""><figcaption></figcaption></figure>

* Enter the name.
* Optionally enter a description.
* Select **Save**.

## Edit portal page

* Hover over the card, click on the three-dot menu to open the context menu, and select **Settings**.
* You can now change the name and description.

## Delete application

* Hover over the card, click on the three-dot menu to open the context menu, and select **Delete**.
* Confirm and the application will be deleted.

{% hint style="danger" %}
Deleting a portal page cannot be undone.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/portal-pages/create-portal-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.