White-Label Portal Overview

The White-Label Portal gives clients a read-only view of their Trakkr data under your agency name. They use a separate client login, see only the brands you grant, and do not enter your internal Agency workspace.

This is more than a shared link. It supports named client accounts, brand or group access, a custom domain, branded email, controlled navigation, and activity logs.

What's included

• Your portal name, logo, favicon, accent colour, and login copy.
• A custom subdomain with HTTPS.
• Branded client email from a verified domain.
• Client access to one or more brands, or a whole brand group.
• A menu you control, with client-facing names for each feature.
• Optional Pages, so a client can inspect page-level detail without editing it.
• Optional Results, so a client can see measured before-and-after outcomes from the work.
• A shared export setting plus a per-client export permission.
• Welcome text, method text, footer links, and copyright text.
• Client activity logs and retention controls.

The portal remains read-only. A client can explore the data and use the exports you allow, but cannot change prompts, competitors, brand settings, Actions, or your agency setup.

What clients can see

Four features form the required base: Dashboard, Competitors, Citations, and Prompts. Reports, Perception, Pages, and Results are optional.

Pages is useful when a client wants to know which URL needs attention. Results is useful when they want to know what changed after the work. Together they let you move from an account-level score to the page, the Action, and the measured outcome without exposing internal operating controls.

See Permissions and Features for the exact controls.

Brand access and group access

A client invite can grant selected brands or one brand group.

Selected-brand access is fixed to the brands on the invite. Group access follows the group: if you add another brand to that group later, the client can see it without a new invite. Use group access for a client with several locations or products that should move together.

Portal users do not consume team seats. They use a separate client permission model and cannot see other clients unless you grant a brand or group that contains them.

Where to configure it

Open Settings: White-Label. Owners and authorised admins can see seven sections:

1. Branding
2. Clients
3. Features
4. Onboarding
5. Footer
6. Email
7. Logs

Domain setup sits above these sections. The Preview action opens the current portal so you can inspect it before inviting anyone.

Access and billing

The Agency workspace and client-facing white-label access are related but not identical. An active Scale trial may open internal Agency tools, but it does not publish a client portal that could disappear when the trial ends. Client-facing access needs the white-label entitlement on a paid Scale-equivalent account or contract.

White-label billing is counted by enabled brand, not by client login. Several client users can access the same enabled brand without creating another brand charge. The invite screen shows the billing effect before you confirm.

A safe launch order

1. Add the portal name, logo, colour, and login copy.
2. Configure the custom domain and wait for HTTPS to become active.
3. Set up branded email and send yourself a test.
4. Choose the visible features. Decide whether Pages and Results are ready for this client.
5. Write the welcome and method text, then check the footer.
6. Open Preview on desktop and mobile.
7. Invite an internal test address with the same access you plan to give the client.
8. Review the test account, then send the client invite.

Common questions

Can a client edit anything?

No. Portal access is read-only. Export access is the only data action you can add.

Can one client see several brands?

Yes. Grant several selected brands, or use group access when future brands in the group should appear automatically.

Can I hide Results for one client but show it to another?

Feature visibility is set on the shared portal menu, so it applies to all portal clients. Brand and export permissions can vary by client.

Do client users count as team seats?

No. Teammates and portal users are separate.

Should clients see every available feature?

Usually not. Start with the views you explain in the service. Add Pages when page detail helps the conversation. Add Results when the client is ready to read measured outcomes, including Couldn't measure as an honest result.