Team, Settings & White Label

What this is for, in one sentence: Team and White Label settings are where your agency becomes the product your clients see — who’s on the team, which clients each person can touch, and whose brand is on every dashboard, invite email, and exported report.

When to come here:

• Onboarding a new analyst or account manager — invite, role, and client scoping in one pass
• Before your first client-facing export, to set the branding that every report will render under
• When someone leaves: revoking access is a single action, and the invitation history keeps the record

Marcus Tan runs eight client workspaces through NorthStar Digital, and two things keep that defensible: nobody on his team sees a client they’re not assigned to, and nothing a client receives says anything but NorthStar. Both are configured here — once — and then confirmed by the rest of the product every time they matter.

---

The team roster

One table answers the three questions that matter about any team: who, what role, which clients. Three roles do the work — Owner (full access, billing, and settings), Account Manager (manages assigned clients and their reports), and Analyst (views data and builds reports for assigned clients). Client access is explicit per member: an Account Manager might carry 3 clients, an Analyst exactly the two they work on, and the Owner sees everything.

Below the roster, Invitation history keeps the audit trail: who was invited, as what, and what happened — Pending, Accepted, or Revoked, each dated. That revoked entry isn’t clutter; it’s your record that a departed contractor’s access was actually cut, with a date you can point to.

Scope access like client confidentiality depends on it — because it does. If two of your clients compete, the analyst on one shouldn’t be browsing the other’s dashboard. Assign the minimum client set per person and let the roster be the proof of it.

Inviting someone — and what the form won’t let you do

The invite flow is email → role → client access, with the role’s plain-language description right under the picker so you’re never guessing what “Analyst” grants. Client access is a checklist of your actual client list — tick exactly the workspaces this person should see.

The form also protects you from yourself: enter an address that’s already on the team and it tells you so (“Already a team member — since Apr 2026”) instead of firing a duplicate invitation. And note the line at the bottom: invites are sent with your branding, not the vendor’s — which is exactly right for the client-facing story, but means your new hire should know what sender name to look for.

White Label

One screen, four levers:

• Logos — sidebar mark and full logo, replacing default branding across the dashboard.
• Branding — your app name and accent color. This is the setting that replaces the vendor’s name across dashboards, team invite emails, and client-facing exports.
• Custom Domain — serve the dashboard from your own address (insights.yourbrand.com), so the address bar tells the same story as the report header. Status shows Active once it’s live.
• Per-client co-branding — show a client’s own logo next to yours on their dashboards and exports, per client. One client can have a custom logo while the rest run your agency default.

This is also the screen every export quietly depends on: the branding block you confirm in Exporting Client Reports before each render is reporting what you configured here.

Configure this before the first client ever sees a screen — not after. Rebranding mid-engagement means a client noticing the change, and the question that follows (“what tool is this really?”) is one you never need to invite. Set it once, send yourself a test export, and let every artifact after that be consistent.

Common questions

What does client scoping actually control? Owners and unrestricted roles see everything; scoped members see their assigned clients only, across dashboards and exports alike.

What does a Pending invite mean, and what if it stalls? Sent but not yet accepted. Check the address, resend, and remember the email arrives under your brand — tell new teammates what sender name to look for.

We rebranded — what has to change here? App name, logos, accent, and (if it changed) the custom domain — one screen. Then re-check per-client co-brands and send yourself a test export before the next client report goes out.

Does the custom domain affect where the team logs in? It’s the branded address for your workspace surfaces — share it as the way in, and the vendor name stays out of the address bar for everyone you’ve invited.

Who should be an Owner? As few people as your continuity plan allows — Owner includes billing and settings. Most of an agency runs correctly on Account Manager + Analyst with clean client scoping.

What to do next

• Exporting Client Reports — the surface this configuration exists for; the branding block there confirms what you set here.
• Getting Started: Adding a Client — the onboarding flow this module’s scoping and co-branding should be part of, day one.
• Visibility Gaps — what your newly-invited analyst should be working from, per client.