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 Member or Viewer — 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 Invitations section 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

Reach it from the sidebar: click Settings to expand it, then choose Team.

Within Team, three sub-tabs split the page, and only three: Members (n) — the roster below, with the live member count carried in the tab label itself — then Quotas, and Permissions. There is no invitations sub-tab; if you’re looking for one, read on.

One table answers who’s on the team, what role they hold, when they joined, and which profiles they can access.

There are three roles. Owner manages the team, billing and settings, and can transfer or delete the organisation. Members can create brand profiles, consume credits, and use all product features. Viewers have read-only access. They can view dashboards and reports but cannot modify anything. The invite form offers Member and Viewer only.

Viewers must be assigned at least one profile, because they can’t create their own.

A Viewer who opens a content or generation tool, such as Content Optimizer, Content Writing, Content Library, LLMs.txt Generator, Schema Generator, Visibility Gaps, Strategic Context or a new Brand Intelligence run, is sent back to the dashboard, even from a direct link.

Pending invitations live inside Members (n) rather than in a tab of their own, and they show up in two places. The summary line under the organisation name counts them next to the roster — “1 member · 0 pending invitations” — so you can tell at a glance whether anything is outstanding. Below the roster table, an Invitations section keeps the audit trail: email, role, status, and expiry, with each invite shown as Pending, Accepted, Expired, or Revoked, and a Resend invitation and Revoke invitation action on every row. That section appears only once at least one invitation exists, and only for people who can manage the team — so a Members tab with no Invitations block under it means nothing is outstanding, not that something is missing. That revoked entry isn’t clutter; it’s your record that a departed contractor’s access was actually cut, with an expiry date you can point to.

Your plan sets how many seats the team can hold: 2 on Starter, 5 on Growth, 10 on Scale and unlimited on Enterprise. Active members, the Owner included, take a seat. So does every pending invitation that hasn’t expired, because an invite reserves the seat it will fill. Revoking an invitation, or letting it expire, frees the seat again. When the team is full, sending another invitation fails with “Seat limit reached (5/5). Upgrade your plan to invite more members.”

Scope access like client confidentiality depends on it — because it does. If two of your clients compete, the person 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 → profiles, with the role’s plain-language description right under the picker so you’re never guessing what “Member” or “Viewer” grants. The Assign Brand Profiles checklist lists your actual profiles, each shown with its URL underneath; tick exactly the ones this person should see. The modal keeps the Send Invitation button in view the whole time, so a long profile list never scrolls it off-screen and leaves you hunting for how to finish.

Every invite gives you a clear outcome — no silent no-ops. Enter an address that’s already on the team and the form tells you so (“Already a team member — since Apr 2026”) instead of firing a duplicate invitation. And if you don’t tick any profiles, the modal doesn’t silently proceed either: it shows “No profiles selected. The invited user will create their own profile during onboarding.”

White label branding

Most accounts will not find this screen, and that is by design rather than a gap. Settings shows four tabs — Account, Profiles, Notifications, and Team — and a fifth White Label tab is added only when you are the organisation’s owner and white label is switched on for your workspace. If the tab isn’t there, the entitlement is what’s missing, not the feature; ask whoever owns your account about the agency tier. Everything below describes the screen as entitled owners see it.

Where it is available, it’s one screen with three cards:

• Logo — a sidebar logo and a full logo, replacing the default branding across the dashboard and on the sign-in pages.
• Branding — your app name and accent colour. 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. It lists the DNS records to add at your provider, and the status beside it moves from Pending DNS to Provisioning SSL to Live.

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 see every profile. Members and Viewers see the profiles assigned to them, 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.

I invited someone who’s already on the team — did it send twice? No. The form recognises an existing member and tells you inline instead of sending a second invitation, so you won’t accidentally double-invite anyone.

How many people can I invite? As many as your plan has free seats: 2 on Starter, 5 on Growth, 10 on Scale, and no limit on Enterprise. Pending invitations count, so a team of 4 on Growth with one invitation outstanding has no seat left to give. Revoke the invitation you no longer need, or upgrade, and the form works again.

Do I have White Label on my plan? Two things have to be true for the tab to appear: white label has to be enabled for your workspace, and you have to be its owner. If a colleague can see the tab and you can’t, it’s the second one — the rest of Team and Settings works the same either way.

Who should be an Owner? As few people as your continuity plan allows — Owner includes billing and settings. Most agencies run on a small number of Owners, Members for the people doing the work, and Viewers for clients or stakeholders who only need to read.

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 Member should be working from, per client.