Team seats: bring your whole team

Until now a PlainDMARC account was one login. Now you can invite your whole team — a colleague who should see everything and change things, or a client who should just watch the verdicts land. Two roles, seats that scale with your plan, and nothing to configure.

Two roles

Every member is one of two things:

• Full access (owner) — everything you can do today: add and remove domains, edit branding, manage billing, invite and remove other members.
• View-only — reads every domain, every weekly verdict, and the sender breakdowns, but changes nothing. Any attempt to write is refused with a plain read-only message. It's the same guarantee a read-only API key gives — visibility without control.

That's the whole model in v1: two roles, easy to reason about. It's the safe way to hand a client a window into their own email health, or give a junior teammate the full picture without the ability to break anything.

Seats scale with your plan

Each plan includes a set number of seats — the member and any pending invites both count against it:

See it on the pricing page, where every plan card shows its seat count next to the domain cap.

Inviting someone takes about a minute

1. Open the Team screen in your dashboard.
2. Enter a teammate's email, pick view-only or full access, and send the invite.
3. They open the link, sign in as that email — which is how PlainDMARC knows it's really them — and they're in.

You can promote a view-only member to full access, or step back to view-only, at any time. An account always keeps at least one full-access owner, so you can't accidentally lock yourselves out.

Downgrades pause, they never delete

If you move to a smaller plan and end up with more members than seats, the extra members are paused — not removed. They keep their place and simply can't act until seats free up; the next upgrade brings them back, owners first. It's the same rule we already use for domains: PlainDMARC never quietly deletes your data because a plan changed.

What's not here yet — plainly

We'd rather tell you the edges than let you find them:

• Two roles, not a full permission matrix. There's owner and view-only — no separate "admin" tier in between.
• A view-only member sees all your domains, not a client-scoped subset. If you need to invite a client and show them only their domain, that's not here yet.
• No SSO or SCIM. Members sign in with the same email magic-link everyone uses.

These are on the list. What shipped is the part most teams actually needed first: a second (and third, and tenth) safe pair of eyes.