> 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/page-builder/page-details-and-basics.md).

# Page Details and Basics

Change an Action Page's internal name and URL slug in the Details panel, and set its internal description and the paused message supporters see in Basics.

The **Details** and **Basics** panels hold the information that identifies your Action Page: its internal name, its URL slug, an internal description, and the message supporters see when the page is paused. You'll find them in the Page Builder under **Page > Details** and **Setup > Basics**. Both panels are available on Donation Pages, Event Pages, and Lead Pages. This article covers each field.

## Before You Begin

* To save changes, you need **Action Pages: Edit permissions**.

## Open Details

To open Details:

1. Go to **Action Pages > Pages**.
2. Click the name of the page you want to edit.
3. Select **Page > Details**.

You can also click the pencil next to the page name at the top of the Page Builder to open Details.

## Details Fields

* **Internal page name:** The name your team sees in Anedot, such as in the Action Pages list. Supporters don't see this name. It's required and can be up to 255 characters.
* **Page URL slug:** The last part of your page's web address. Use lowercase letters, numbers, dashes, and underscores only.

To set the heading supporters see at the top of your page, go to **Page > Branding** and use **Header title** in the **Header** section. Event Pages hide this field and use the event name as their title. To learn more, see [Branding](/action-pages/page-builder/branding.md).

{% hint style="warning" %}
If you change the **Page URL slug** and save, links that use the old address stop working. Update any links, buttons, and emails that point to the old address. **Share** stays unavailable until you save the new slug.
{% endhint %}

When you're done, click **Save**.

## Open Basics

To open Basics:

1. Go to **Action Pages > Pages**.
2. Click the name of the page you want to edit.
3. Select **Setup > Basics**.

The panel's heading reads **Settings**.

## Basics Fields

* **Description:** An optional internal description of the page, for your team's notes. Supporters don't see it.
* **Paused message:** The message supporters see when the page is paused.

{% hint style="info" %}
New pages start with the placeholder paused message "DEFAULT PAUSED MESSAGE." Replace it with your own message so supporters know what to do if they visit while the page is paused.
{% endhint %}

You pause and resume a page from the Action Pages list, not from the Page Builder. To learn how, see [Pause or Archive an Action Page](/action-pages/action-page-basics/pause-or-archive-an-action-page.md).

When you're done, click **Save**.

## Troubleshooting

* **"Page name is required."** Enter an **Internal page name**, then save again.
* **"Page URL is required."** Enter a **Page URL slug**, then save again.
* **"Use only letters, numbers, dashes, and underscores."** Remove spaces and other characters from the **Page URL slug**, then save again.
* **The page won't save after you change the slug:** Make sure the slug uses lowercase letters only.

## Related Articles

* [Page Builder Overview](/action-pages/page-builder.md)
* [Branding](/action-pages/page-builder/branding.md)
* [Share an Action Page](/action-pages/action-page-basics/share-an-action-page.md)
* [Pause or Archive an Action Page](/action-pages/action-page-basics/pause-or-archive-an-action-page.md)
* [Create, Edit, and Clone](/action-pages/action-page-basics/create-edit-and-clone.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/page-builder/page-details-and-basics.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.