Organization & members

Every property, banner design, and consent record belongs to an organization — the top-level container your team collaborates in. This guide covers switching between organizations, inviting teammates, and what each role can and can't do.

Organizations

The organization switcher sits at the top of the sidebar, showing the active org's name and your role badge inside it. Click it to open a dropdown listing every organization you belong to, each with its own role badge, plus:

• Switch — click any org row to make it active. This reloads the dashboard scoped to that org: properties, banner designs, members, usage — everything you see changes to that org's data.

• New org — opens a small dialog asking for a name. Submitting it creates the organization and makes you its Owner, then switches you into it immediately.

If you're already at your account's organization limit, New org shows an upgrade prompt instead of the create dialog, linking straight to Account → Plan & usage.

How many organizations you may own is capped by your account's plan (Free: 1, Starter: 3, Pro: 10, Scale: unlimited). Being invited as a member into someone else's org doesn't count against this limit — you can belong to as many orgs as people invite you into.

Team & roles

Go to Account → Team (the Team section on the Account page) to see everyone with access to the current organization. Each row shows an email and a role. To add someone:

1. Click Invite member.

2. Enter their email.

3. Choose a role: Admin, Member, or Viewer.

4. Click Send invite.

If the email is already a member of this org, the invite is rejected with a clear "already a member" message rather than creating a duplicate. If you're at your plan's seat limit, Invite member is disabled and a hint links to the plan picker.

Roles

You can change anyone's role except the Owner's from the dropdown next to their name in the member list — it takes effect immediately, no confirmation step. To revoke access entirely, click Remove on their row; a confirmation dialog names the person before you commit, and once confirmed they lose access right away.

Role enforcement happens server-side, not just as disabled buttons in the UI — a Viewer's API calls against configuration endpoints are rejected the same way the corresponding buttons are hidden or disabled for them in the dashboard. Don't rely on UI-only restrictions when reasoning about what a role can reach.

Seats and usage

Seats are counted per organization and gated by plan: Free allows 1, Starter 3, Pro 10, Scale unlimited. The Team card shows a live used / limit counter next to its title once you're on a plan with a finite seat count. Inviting past the limit is blocked at invite time (not after the fact), with a link to upgrade.

Multiple organizations, one account

A single login can belong to many organizations at once — useful if you manage properties for more than one company, or if you're a contractor invited into a client's org while also owning your own. There's nothing to configure for this; it falls out naturally from accepting invites and/or creating additional orgs, and the switcher is how you move between them. Nothing you do in one org (properties, members, banner designs) is visible from another — the isolation is complete except for you personally appearing in both member lists.

Tips and gotchas

• Invite people with the lowest role that lets them do their job — Viewer for stakeholders who just need visibility, Member for day-to-day banner/property work, Admin only for people who should also manage the team itself.

• Removing someone is immediate and has no undo from this screen — if in doubt, demote to Viewer first rather than removing outright, then remove later once you're sure.

• The Owner can't be changed or removed from the Team page by design; if ownership genuinely needs to transfer, that's not a self-service action from this screen.

• Seat limits are checked against your current organization's plan — the same person occupies a seat in every org they're a member of, each counted independently.

Next steps

• Plans & billing — seat limits, org-ownership limits, and feature gating per tier.

• Properties — the domains this organization protects.

• Account security — password, sessions, and connected sign-in methods for your own account (separate from org membership).