> ## Documentation Index > Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt > Use this file to discover all available pages before exploring further. # Client portal > Give clients a branded, secure home for their events — contracts, invoices, forms, and updates — mapped to their record in your CRM. The client portal rolls out per organization. If you don't see portal actions on your customers, [contact support](mailto:support@soundcheck.live) to enable it. The client portal is a branded, secure space where your clients see their own events and everything that goes with them — the agreements to sign, the forms to fill out, the invoices you've shared, and updates from your team. Instead of chasing signatures and answers across email, you invite the client once and they have a single place to act. Each client's portal maps to their record in your CRM: you invite a customer's primary contact, they sign in, and from then on they see only their own [customer's](/crm/customers) events and documents. ## What clients see The portal has its own navigation, separate from your staff workspace. In the portal, your gigs are labeled **Events** — the client-facing word for the same thing. A welcome home base: what needs the client's attention, upcoming events, an open-balance summary, contracts awaiting signature, and recent invoices. Every event linked to the client, each opening to its own workspace with the details your team has shared. Agreements shared across their events, with in-portal e-signing. Deposits, balances, and payment requests your team shares — a clear view of what's due and what's paid. Questionnaires and intake forms the client needs to complete, filled out right in the portal. Updates and replies from your booking team, organized per event instead of long email threads. The contact information you have on file, plus session and sign-out controls. ### The dashboard The dashboard leads with an **Action Required** panel when there's something to do — a contract to sign or a form to fill. Below it, stat cards summarize **upcoming events, open balance, contracts awaiting signature, and active events**, followed by the client's next few events and most recent invoices. ### An event's workspace Opening an event gives the client a focused workspace with tabs for its **overview** (date, location, status), **contracts**, **forms**, shared **notes**, **payments**, **files**, and **messages**. An event switcher lets them hop between their other events without leaving the workspace. If a form still needs their attention, the overview calls it out. Payments, files, and messages are surfaces your booking team shares into — a client sees content there when your team provides it, and an empty state until then. Contracts and forms are the portal's most active surfaces day to day. ## Your brand, not ours The portal carries your organization's branding — name, logo, and colors — so it feels like an extension of your business rather than a third-party tool. This ties in with [white-label contract signing](/features/contracts/white-label-branding) so the whole client experience stays on-brand. ## How it maps to your CRM Everything a client sees is scoped to their [customer](/crm/customers) record: * You invite a customer's **primary contact** to the portal. * When they accept and sign in, their account is bound to that contact and customer. * The portal then shows only that customer's events, contracts, invoices, and forms. Because the mapping runs through your CRM, the work you already do — [converting leads](/crm/leads/converting-leads), linking gigs to customers, assigning [portal forms](/crm/integrations/portal-forms) — is what populates each client's portal. Before you invite anyone, you can **preview** any customer's portal to see exactly what they'll get. See [inviting clients](/features/client-portal/inviting-clients). ## Related pages Send an invite, preview the portal, and manage access. What clients do in the portal. The CRM records the portal maps to.