> ## 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. # The admin Dashboard > See your hubs, the alerts that need you, and your team at a glance, and create a hub from the Membership.io admin Dashboard. The **Dashboard** is the overview page of the admin at [app.member.dev](https://app.member.dev). It shows the open alerts that need an owner's attention and the active team's hubs, on one page. A few terms first: * A **team** is the workspace that owns your hubs, media, and API keys. See [Tenancy](/concepts/tenancy). * The **active team** is the team the admin is working in right now. The Dashboard shows that team's data and changes when you switch teams. See [Switch teams](/guides/platform-account#switch-teams). * A **hub** is the branded destination your members visit. See [Mental model](/concepts/mental-model#hub). The page is titled **Dashboard** and has two blocks, one under the other: **Needs you**, when there is something to show, and **Your hubs**. **New hub** sits at the top right of **Your hubs**. The page does not show team-wide numbers or a team summary yet. ## Needs you **Needs you** lists the open admin alerts for the active team. These are problems the system found that an owner should look at, such as a Stripe product or price that was archived in Stripe, a payment event that arrived for a customer with no email, a paused drip campaign, or a Stripe sync that failed. Each row shows: * The alert as a short sentence, such as "Stripe archived a product you still sell" or "Stripe sync failed". * The hub's name, when the alert belongs to a hub you can still read, then the date it was raised. * An **Open hub** button, when the alert belongs to a hub. It opens that hub's workspace. Alerts that are not tied to a hub have no button. The admin loads the five newest open alerts and orders those, so an older urgent alert can be missing from the block; **Notifications** has them all. The order puts Stripe archive and drift problems and quota alerts first, then notices (such as a paused drip campaign), then types the admin does not recognize yet, which includes Stripe sync failures. Within the same group, newer alerts come first. The block shows those alerts and a **See all** link that opens the **Notifications** page. If there are more than five, it adds "More alerts need you." While alerts load, the block shows placeholder rows. If there are no open alerts, the list is not drawn. Only the team owner can see alerts. Anyone else sees "Only the team owner can see alerts." If alerts fail to load, you see "We couldn't load your alerts." with a **Try again** button. If a refresh fails while alerts are already showing, you see "We couldn't refresh your alerts. Your last loaded alerts are still shown." with **Try again**. ## Your hubs **Your hubs** lists every hub in the active team as a table: | Column | What it shows | | - | - | | Hub | The hub's name and slug. | | Access | A **Private** or **Public** badge. | | Needs you | How many open alerts belong to the hub, or **Nothing**. This column appears only once every open alert has loaded. | * Select a row, or the hub's name, to open the hub's admin workspace. See [Open or manage a hub](/guides/admin-getting-started#4-open-or-manage-a-hub). * The eye button at the end of a row opens the member-facing hub in a new tab. Its tooltip says "Open as members see it". It shows when you point at the row, always on touch screens, and not at all when the admin environment has no hub address configured. * On a phone the table keeps only the first cell. The access, the **Needs you** count, and the eye button move under the hub's name. The table shows the first eight hubs. If you have more, the last row says **Show all N hubs**; select it to see every loaded hub, and **Show fewer** to go back. When the team has more hubs than the first page, the row says **Show all hubs** instead of a count, and once the list is expanded, **Load more** under the table brings in the rest. If a load fails, you see "We couldn't load more hubs." and a **Try again** button. When there are no hubs, the block shows **No hubs yet** and "Create a hub for your membership community." with a **Create hub** button. If the hubs cannot be loaded, you see "We couldn't load your hubs." and a **Try again** button; if a refresh fails while hubs are showing, the message is "We couldn't refresh your hubs. Your last loaded hubs are still shown." If you are not allowed to see the team's hubs, the block says "You don't have access to this team's hubs." ## Create hub Select **New hub** next to **Your hubs**, or **Create hub** in the **No hubs yet** state. On a narrow header **New hub** collapses to its icon. This opens the same dialog as the **Hubs** page: one **Hub name** field, a note that "Your hub starts from the Starter template. You can change everything later.", **Cancel**, and **Create hub**. The slug is made from the name. The **Slug** field appears only if the slug is invalid or already taken, so you can fix it. See [Slug rules](/guides/admin-getting-started#slug-rules). When the hub is created, the admin opens its workspace. If you switch teams while the dialog is open, it closes and its draft is discarded, so a hub is never created in the wrong team. ## Next steps * [Getting started in the admin](/guides/admin-getting-started): create your account and your first hub. * [Your account and team](/guides/platform-account): your profile, password, team members, and payment accounts. * [Manage API keys in the admin](/guides/platform-api-keys): create the keys your integrations use. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.