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

# Override Plans Page

By default the page at /subscribe will show your active subscription plans. From here your customers can choose the plan they want to sign up for, then proceed to subscribe.

You can override this default view by creating a page with a page slug of "subscribe". The page title can be whatever you wish, so long as the page slug is "subscribe".

1. Create a new page, and title it "Subscribe."
2. After creation, you can change the title, but leave the slug as "subscribe".
3. Click the "Build your Page" button.
4. Add the Subscription Plans page leaf
5. Configure plans to display
6. Eat a cookie!

Mavenseed will detect that you have a custom subscribe page, and will instead show the contents of your new page. 

From here you can use the page builder to build the page. 

To show subscription plans, use the Subscription Plans page leaf, and configure the subscription plans that you'd like to have displayed.


---

# 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.mavenseed.com/admin/subscriptions/override-plans-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.