# Status pages A status page tells your customers whether your services are working, what is wrong when they are not, and what work is planned. This page walks through creating one, choosing its layout and branding, and putting it live. ## How a status page fits together A status page is made of a few parts, each covered on its own page: | Part | What it is | |------|-----------| | [Components](https://docs-dev.evohub.io/components-and-groups.md) | The services visitors see a status for, such as "API" or "Dashboard". A component's status is set by hand or follows an uptime monitor. | | [Component groups](https://docs-dev.evohub.io/components-and-groups.md#component-groups) | Optional groups of components, one per product, region or service. | | [Incidents and maintenance](https://docs-dev.evohub.io/status-incidents-and-maintenance.md) | Published from On-Call and shown on the page with their updates. | | [Subscribers](https://docs-dev.evohub.io/subscribers.md) | Visitors who follow the page by email or through an RSS/Atom feed. | | [Custom domain](https://docs-dev.evohub.io/status-page-custom-domain.md) | The address the page is served on, such as `status.example.com`. | Status pages live under **Status Page** in the EvoHub console. The **Pages** list shows every page in your organization. If you pick a team in the team switcher, the list shows that team's pages. ## Create a status page :::steps ### Open Status Page In the EvoHub console, open **Status Page** from the **Services** menu. ### Start a new page Click **New Page** (or **Create your status page** if you have none yet). ### Name it and add a logo Enter a **Name**, for example `Acme Status`. You can upload a logo now (PNG, JPEG, WebP or SVG, up to 2 MB) or paste a logo URL. Both are optional and can be changed later. ### Create Click **Create Page**. EvoHub opens the new page's settings. ::: A page created while a team is selected in the team switcher belongs to that team. ## The page settings Each status page has five tabs: | Tab | What you do there | |-----|------------------| | **Components** | Add components, group them, set their status and pick the public layout. | | **Incidents** | See the incidents and scheduled maintenance published to this page. | | **Subscribers** | Turn email subscriptions on or off and see who is subscribed. | | **Appearance** | Page text, links, analytics, history window, logo, favicon and theme. | | **Domain** | Connect your custom domain, and delete the page. | Use **Edit page** in the header to rename the page or change **Publicly accessible**. ## Choose a public layout Once a page has components, the **Components** tab shows **Public page layout**. It decides how visitors see your components: | Layout | What visitors see | |--------|------------------| | **One list** (default) | Every component in one plain list. Group names are not shown. | | **Folded groups** | Each group folds into one line with its worst status and one uptime bar. Visitors can open a group to see its components. | | **A page per group** | The main page shows a card for each group, and each group has its own page at an address made from its name, such as `status.example.com/payments`. | The two grouped layouts need at least one group. See [Components and groups](https://docs-dev.evohub.io/components-and-groups.md) for how to create groups, choose which groups start open, and the limit on **A page per group**. ## Brand the page Open the **Appearance** tab. **Customization** holds the page's text and links. Click **Save customization** when you are done. | Field | What it does | |-------|-------------| | **Page description** | Shown under the header on the public page. | | **Footer text** | Small print at the bottom of the page, for example `© 2026 Acme`. | | **Support URL** | Where the support link in the header points. Use a `mailto:` or `https:` address. The link only appears when this is set. | | **Support button label** | The text of that link. Defaults to **Report a problem**. | | **Privacy policy URL** / **Terms of service URL** | Linked in the footer. | | **Google Analytics tag** | A tag such as `G-XXXXXXX`. Page views are sent to your Google Analytics property. | | **History window** | How far back the uptime bars and the incident calendar go: **30 days** or **90 days** (the default). | | **Show this page in search engine results** | Clear it to ask search engines not to index the page. | The other cards on the tab: - **Logo**: shown in the page header instead of the page name. PNG, JPEG, WebP or SVG, up to 2 MB. - **Favicon**: the browser-tab icon. If you do not set one, the logo is used. - **Public page theme**: **Light** or **Dark**. Visitors see the page in the theme you pick. Every public page also has a small "Powered by EvoHub" link in the footer. ## Publish the page A status page goes live on your own domain. Until you connect one, **View public page** is disabled. :::steps ### Add components On the **Components** tab, add the services you want to show. See [Components and groups](https://docs-dev.evohub.io/components-and-groups.md). ### Connect a domain On the **Domain** tab, connect a subdomain such as `status.example.com` and add the DNS records the console shows. See [Custom domain](https://docs-dev.evohub.io/status-page-custom-domain.md). ### Check it When the domain shows **Verified · SSL active**, click **View public page**. ::: Changes you make in the console, and incidents published from On-Call, reach visitors within about 30 seconds. An open public page refreshes itself, so visitors do not need to reload. ### Hide a page without deleting it Click **Edit page** and clear **Publicly accessible**. Visitors to your domain then see "This status page is not configured", and the page's feeds stop working. Turn it back on to restore the page. ## Delete a status page On the **Domain** tab, under **Danger Zone**, click **Delete page**. Type the page's name to confirm, then click **Delete permanently**. > [!WARNING] > Deleting a page permanently removes its public page, components, incidents, maintenance windows and connected custom domain. It cannot be undone. ## Who can do what Status page actions follow your organization role. The permissions involved are: | Action | Permission | |--------|-----------| | Create, edit, brand, publish or delete a page; connect a domain | `status:page:write` | | Add, edit, reorder and group components; set a component's status | `status:component:write` | | See incidents / maintenance on the page | `status:incident:read` / `status:maintenance:read` | | See subscribers / remove subscribers and change subscription settings | `status:subscriber:read` / `status:subscriber:write` | The built-in Owner, Admin and Member roles hold all of these. Viewers can see pages but not change them. See [Roles and permissions](https://docs-dev.evohub.io/roles-and-permissions.md). ## Billing Status pages are billed by usage. See [How billing works](https://docs-dev.evohub.io/how-billing-works.md) for what is metered and the current rates. ## Related - [Components and groups](https://docs-dev.evohub.io/components-and-groups.md) - [Incidents and maintenance](https://docs-dev.evohub.io/status-incidents-and-maintenance.md) - [Custom domain](https://docs-dev.evohub.io/status-page-custom-domain.md) - [Subscribers](https://docs-dev.evohub.io/subscribers.md)