> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/action-page-basics/manage-pages.md).

# Manage Pages

Access the Pages Index by navigating to Action Pages → Pages within your fundraising account.

Access the **Pages Index** by navigating to **Action Pages → Pages** within your fundraising account. From here, you can create new Action Pages, search and filter existing ones, manage page settings, and view submission data.

## + New Page

Click **+ New Page** to create a new **Donation**, **Lead**, or **Event** page.

* **Donation Pages** – Financial pages where supporters can submit donations.
* **Lead Pages** – Non-financial pages used for petitions, surveys, and lead collection.
* **Event Pages** – Pages for ticketed events.

## Search Bar

Search by **Page Name**, **Page Slug**, or **Page ID** to locate specific Action Pages.

## Tags (Icon)

Click the **Tags** icon to create or manage tags for your pages.

* Tags can be used to organize and filter pages.
* Removing a Team tag removes that Team's access to the page.

## Filter

Use the **Filter** menu to find pages by **Tag** or **Status**.

## Page Row Menu

Hover over a page row and open the **⋮** menu:

* **Edit** – Opens the Builder to modify the page.
* **Copy page URL** – Copies the public page URL.
* **Open page** – Opens the public view of the Action Page.
* **View submissions** – Displays all submissions for the page.
  * To view Submissions for an Event Page, follow the steps below:
    1. Copy the Event Page ID
    2. Access Action Pages → Submissions from the main menu
    3. Filter Submissions by the copied Page ID
    4. Create a CSV export to view all submissions made through the Event Page
* **View transactions** – Opens Finance transactions for the page.
* **Clone** – Creates a copy of the page.
* **Pause** – Stops new submissions from being processed.
* **Resume** – Reactivates a paused page so it can accept submissions again.
* **Archive** – Permanently archives the page *(must be paused first)*.

## Status

Pages can have one of three statuses:

* **Active** – Live and accepting submissions.
* **Paused** – Not accepting new submissions.
* **Archived** – Removed from active use.

## Tags (Column)

Shows tags assigned to each page for organization and filtering purposes.

## Page Type

Indicates whether the page is a **Donation Page**, **Lead Page**, or **Event Page**.

## ID

Each Action Page has a unique **ID**, used for tracking within Anedot.

## Submission Count

Displays the number of submissions *(successful and failed)* for the page.

> ***Tip:** This number may differ from data in the Transactions tab, as failed submissions are also counted here.*

## Related

* [Tandem Pages](/action-pages/advanced-features/tandem-pages.md)
* [Share an Action Page](/action-pages/action-page-basics/share-an-action-page.md)
* [Tracking Codes for Action Pages](/action-pages/advanced-features/tracking-codes-for-action-pages.md)
* [Terminal](/finance/internal-processing/terminal.md)
* [Manage Events](/action-pages/action-page-basics/manage-events.md)


---

# 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.anedot.com/action-pages/action-page-basics/manage-pages.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.