<!--
  Translated by the docs agent from content-src/es/guides/primeros-pasos-partner/01-que-es-la-consola-del-partner.md
  (source_hash 1a7623e81881). If that Spanish source_hash changes, re-check this translation.
-->

The **partner console** is a third application, separate from client agencies' Platform and from staff's
internal panel: it lives at `/partner/*` inside the same Admin app (locally, `localhost:3001/partner/login`)
but with its own login and its own visual identity. It's the panel for a **white-label partner**: a company
that resells the Platform to its own customers under its own brand, manages its portfolio of tenants,
charges its customers (or pays a seat fee to the Platform), and customizes the look those customers see.

The console's sidebar gathers its sections in this order: **Overview** (this manual), **Customers** (Manual
38), **Wallet** and **Billing** (Manual 39), **Brand**, **Referrals**, **Team** and **Activity** (Manual
41), **Plans** — your own catalog of plans, including custom ones (Manual 40, section 1, and Manual 38,
section 5) — and **AI** (Manual 40), **Announcements** (Manual 41) and **Support** (Manual 42). "My
account", with two-factor verification, opens from your profile menu at the top right (Manual 42).

> **Note — "Referrals" may not show up in your menu**
>
> If your account is in **White label** mode and has never had any referral yet (not a single commission,
> not even from one who has already unsubscribed), the menu doesn't show "Referrals" — it doesn't apply to
> how you work, so it doesn't take up space. As soon as you have your first active referral, it shows up
> again on its own. If your account is in **Referral** mode, "Referrals" always shows, whatever your
> activity — it's the center of your console (Manual 54 "Referrals: how the money works").

## Roles within the console: Owner and Member

Every partner console account has one of these two roles:

| Role | Scope |
| --- | --- |
| Owner | Full access to the console: everything a Member has, plus financial or organization-wide actions — topping up the Wallet, your seat quota and manual charging (Manual 39), creating/versioning your own plans and managing BYOK credentials/activating models in AI (Manual 40), Brand and your own Domain, Announcements to all your tenants, and Team (inviting and deactivating users, Manual 41). |
| Member | An account invited by an Owner, with access to the same console but **read-only** on the actions above. They CAN carry out, on equal footing with the Owner, the day-to-day operational actions: signing up a new tenant, entering a customer's panel (impersonation), connecting their WhatsApp, and managing support tickets — none of these is exclusive to the Owner. |

> **Note — Wallet, Billing, Plans, AI, Brand, Domain, Announcements and Team belong to the Owner**
>
> These are the financial actions or the ones that affect your whole partner account at once — the real
> permission (`partner:wallet.manage`, `partner:billing.manage`, `partner:plans.manage`,
> `partner:credentials.manage`, `partner:branding.manage`, `partner:domain.manage`,
> `partner:announcements.manage`, `partner:users.manage`) is only held by the Owner role; a Member sees
> those screens, but their write buttons are hidden or the action is rejected if forced. As with the rest
> of the platform, the backend is the source of truth for permissions.