Invite publishers, buyers, and team members

Inviting someone to Moja is not the same as creating a publisher or buyer record, and it is not the same as sending them traffic. The invite only creates a login with a role. What they can see depends on that role and whether their email is attached to the right record.

Roles you can invite

Invite as	Who they are	What they see after they accept	What they cannot do
Admin	Someone on your team who should run the account	The full organization: campaigns, routing, numbers, buyers, publishers, reporting, billing, invites	Treat admin as full control
Editor	Someone on your team who handles day-to-day setup and reporting but should not manage billing or people	The whole organization for operations: campaigns, numbers, buyers, publishers, targets, routing plans, call flows, and reporting (including QAI analysis where enabled)	Cannot access billing, invite members or change roles, open the Audit log, or manage organization API keys
Member	Someone on your team who should work in the account without owning it	Organization tools and reporting for your campaigns	Do not use Member for a publisher or buyer — they will not map to a publisher/buyer record
Publisher	A traffic source / media partner	Reporting and campaigns tied to the publisher record whose email matches their login	Cannot pause a single campaign. Cannot see other publishers. Cannot change your routing
Buyer	A destination / buying partner	Buyer-facing information for the buyer record whose email matches their login	Cannot pause or resume Targets or RTB routes from the buyer portal. An organization admin must change the Target or RTB formula

Rule of thumb: invite publishers as Publisher, buyers as Buyer, and your own staff as Admin, Editor, or Member.

Send an invite (path)

1. Sign in as an Admin.
2. Open Admin → My account → Organization.
3. Open the Members tab and choose Invite.
4. Enter the person’s email, choose the role (Admin, Editor, Member, Publisher, or Buyer), and send the invite.

They must click Accept in the email. Signing in without accepting looks like the account does not exist.

To move an existing team member to Editor, an Admin opens Admin → My account → Organization, opens that member’s role menu, and selects Editor.

Publisher invites

Do this in order:

1. Create the publisher record (Publishers → Create New) with the email they will use to log in.
2. Invite that same email with the Publisher role.
3. They accept the invite.
4. Attach traffic separately (campaign Number Group and/or Inbound RTB publisher). The invite does not send them calls.

The login email must match the email on the publisher record. A matching login without an accepted invite cannot sign in. An accepted invite without that email on the publisher record can open the portal but will not show that publisher’s campaigns.

If they need more people on the same publisher account, they add extra emails themselves: profile → Manage Account → Add Email Address. Administrators cannot add those extra emails on their behalf. See How can my buyer or publisher add more emails associated with their account?

Publisher logins cannot pause one campaign. Stopping traffic is an admin action on Number Group, number pause, inbound endpoint active, or Publisher Is Active. Details: Create, invite, and pause a publisher.

Buyer invites

Do this in order:

1. Create the buyer record (Buyers → Create New) with the email they will use to log in.
2. Invite that same email with the Buyer role.
3. They accept the invite.
4. Attach routing separately (Target, outbound RTB formula, and/or RTB group). The invite does not send them calls.

Same email‑match rule as publishers. Wrong email → they may sign in and see little or nothing of that buyer.

Buyer portal access does not pause traffic. An admin pauses the Target or RTB formula. There is no buyer equivalent of Publisher Is Active; to stop all traffic, an admin must disable every Target and RTB formula that can reach that buyer. Extra emails: same self‑serve Manage Account flow as publishers. Details: Create, invite, and pause a buyer.

Troubleshooting patterns

What happened	Usual cause	Fix
Invite sent, they say they have no account	They signed in without Accept on the invite email	Resend / have them use the Accept link
They signed in but see no campaigns	Publisher/buyer role, but email is not on that record (or they were invited as Member/Editor/Admin by mistake)	Match emails, or re‑invite with the correct role
They see the whole account	Invited as Admin, Editor, or Member instead of Publisher/Buyer	Remove that membership; invite again as Publisher or Buyer
Two people need the same publisher or buyer view	Second person was invited as a new publisher/buyer, or admin tried to add the email	Primary user adds the extra email under Manage Account
Publisher wants to pause one campaign	Publisher login cannot do that	Admin uses Number Group / endpoint / Publisher Is Active
Buyer wants traffic stopped now	Buyer login does not control routing	Admin disables the Target or RTB formula

Quick chooser

Person	Create a record first?	Invite role
Your operator / CS / billing	No	Admin or Member
Your operator who handles setup and reporting but not billing or people	No	Editor
Traffic source	Yes — Publishers, with their login email	Publisher
Call destination / buying partner	Yes — Buyers, with their login email	Buyer