> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Subscription page: review

> Multiple subscription pages, accessibility, personalization, Axottle themes, ads, and Remnawave link.

The Subscription Page is a public website that the customer opens via the subscription link: add buttons to the application, QR code and connections. In **Infrastructure → Subscription Page** (`/new/subscription-page`) Axottle manages the installation and observation of pages, as well as the registration of subscriptions of the selected Remnawave connection.

## Several pages.

At the top of the section, select the desired page. The button **Add page Z** opens two scenarios:

* **Create a new** - install the page via Axottle using SSH or an issued command.
* **Connect an existing one** Add a working Remnawave Subscription Page after checking its public HTTPS address.

Each page has its own domain, status, history, and Remnawave connection. Personal settings and ads are common to the pages of the same Remnawave connection. When you switch the page, check which connection is selected.

To deliver personalized changes, subscription requests must go through the gateway that is part of the Axottle managed installation. Details - [Installation and connection](https://docs.axottle.com/en/subscription-page/installation.md).

## Sections of the page

| Section | What's inside | |
| - | - | - |
| Review | Availability, Certificate and Issuance Status of | |
| Design | User selection, title, theme, personal Flow and messages | |
| Themes Axottle | Theme Gallery Happ and selection of theme in the user's draft | |
| Announcements | Messages to all users, groups, or selected | recipients |
| Integration | Communication with Remnawave, browser response rules and delivery verification | |
| API | Integration methods for bot, billing or support | |
| History | Checks and other operations of the selected page | |
| Control | Update and delete recording from the | panel |

On the wide screen, the sections are on the left, the phone is selected from the list, and the actions available depend on the rights of the account.

## Where does the subscription come from?

Remnawave remains the source of users, accessible profiles, keys, subscription terms and traffic. Axottle adds design, messages, selection and ordering of already authorized profiles. These settings do not provide access to other people's Flow and do not change the keys inside configurations.

Changes come to the app the next time you update your subscription, and the preview in the dashboard shows you how you're going to get it, but it doesn't confirm that you've already received it.

General Flow accessibility rules are configured in **Flow → Settings → Subscription Issuance**. Personal selection on the subscription page applies subject to these rules. More - [registration and Flow](https://docs.axottle.com/en/subscription-page/presentation.md).

## Why a separate server

A separate, clean Linux server is recommended for a public page; pairing with a panel or node increases the overall load and requires verification of port owners, and the wizard warns if it recognizes such a machine at the address.

Supported managed proxy can serve a page on an existing node; an external proxy can be manually installed with a local port; matching with an Axottle status page is not supported. The choice of topology is described in the [Installation Instructions](https://docs.axottle.com/en/subscription-page/installation.md).

## Rights and restrictions

| Right | Features | |
| - | - | - |
| `subscription_page.view` | Page View, Status, Integration and History of | |
| `subscription_page.deploy` | Installation, External Page Connection, Management and Deletion of | Record |
| `remnawave.view` | Reading and Preview of | |
| `remnawave.manage` | Save personal settings and announcements | |
| `connection_units.view` / `connection_units.apply` | View / change the Flow output in its | settings |

The [presentation API](https://docs.axottle.com/en/subscription-page/api.md) uses separate tokens with specific scopes.

Axottle checks the public address and the certificate automatically and on the **button Check**. For the externally connected page, the update is performed on the original server. The `SUB_PUBLIC_DOMAIN` domain in the Remnawave environment is set separately - [communication with Remnawave](https://docs.axottle.com/en/subscription-page/remnawave.md).

## Verification

Check the availability of the page, the certificate term and live delivery through integration. Open the test link in the browser and the client. For registration, additionally save the test setting, update your in-app subscription, and compare the result with the preview.

## Rollback

Personal settings can be reset in the user's card; ads can be turned off or deleted. Changes to the Flow output are returned in the settings of the corresponding Flow.

**Remove from the** panel deletes the observation record, but does not stop the page server and does not revoke the original Remnawave links. For the managed page, deleting the record also revokes the Axottle registration link: the original SERP continues to work. Before disabling, check what personal and general rules depended on this connection.

Related pages: [Installation](https://docs.axottle.com/en/subscription-page/installation.md), [Registration](https://docs.axottle.com/en/subscription-page/presentation.md), [ads](https://docs.axottle.com/en/subscription-page/announcements.md), [API](https://docs.axottle.com/en/subscription-page/api.md).

To design, you need a compatible version of the installed page; connecting an external address by itself does not update it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.