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

# Hub Home in the admin

> What the Home page of a hub shows: member stats, the alerts that need you, and the setup steps left to do.

**Home** is the first page of a hub in the admin. It gives you a quick read on the hub: how many members it has, what needs your attention, and what is left to set up.

## Page layout

On a desktop the page is titled **Overview**, followed by a dot and the hub's name. On a phone the title is just **Overview**, and the stats row scrolls sideways. Below the stats, a **Needs you** tab and a **Get started** tab share one list.

## Open the live hub

The **Open hub** button at the top right opens the hub's public address in a new tab. It appears once the hub has loaded, and only when the admin environment has a hub address configured.

## Stats

The first block shows three numbers:

* **new members, last 30 days**
* **members active in the last 30 days**
* **members with active access, all time**

Only the team owner can see them. Anyone else sees **Only the team owner can see hub stats.** If the stats fail to load, the block shows **Couldn't load stats.** with a **Retry** button. If a refresh fails after the numbers loaded, the block keeps showing the last numbers and says **Couldn't refresh stats. Showing the last loaded numbers.**

## Needs you

The **Needs you** tab, with a count of open alerts, lists the open alerts for this hub only. Alerts that belong to the whole team, not one hub, appear on the team's [Notifications](/guides/admin-notifications) page instead. Alerts are grouped under **Payments**, **Email**, and **Other alerts**; a group with no alerts is left out. Each row shows what happened and, when you open it, a short explanation and a button that goes to where it can be fixed, such as **Open payments**. If the destination page is not available yet, the button falls back to **Open hub**, and an alert with no destination has no button. When nothing is open, the block shows **All caught up**: "Failed payments, reports and domain problems show up here."

The list loads in batches. Select **Load more** to see further alerts. Only the team owner can see alerts; anyone else sees **Only the team owner can see alerts.** If a load fails, the block shows **Couldn't load alerts.** or **Couldn't load more alerts.** with a **Retry** button. If a refresh fails while alerts are showing, it says **Couldn't refresh alerts. This may be out of date.** with **Retry**.

Alerts here are read-only. There is no way to dismiss or mark them as done yet. To see every alert for the team, open the team's Notifications page.

## Get started

The **Get started** tab, with a count of open steps, lists setup steps for this hub that the admin can check for you. It appears only while there is a step to show. Each step opens in place to a button that goes to the right page, and the first open step starts expanded:

* **Create your first page** ("Create the page members land on first."), marked **Required**, shown when the hub has no pages. Its button opens the hub's **Pages** list.
* **Connect Stripe**, or **Finish connecting Stripe** when you have started but not completed it. Its button opens the hub's **Payments** page.

A step disappears as soon as it is done, and the tab disappears when every step is done. If a check fails, the tab shows **Couldn't check Stripe setup.** or **Couldn't check pages setup.** with a **Retry** button, or says you do not have permission to check it. Steps the admin cannot verify, such as branding, are not listed.

## Not shown yet

The activity feed of recent member activity is not part of the page yet.

## Related

* [Notifications in the admin](/guides/admin-notifications)
* [Getting started in the admin](/guides/admin-getting-started)


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