Team members

Invite a teammate

In Native Notify, open Settings (the gear icon, top right) → Team Members, enter their email, pick Admin or Developer (the default) and click Add member. A member can use every app in your account: sending, scheduling, the notification inbox, subscribers, analytics and AI Push. Access is live: a new member sees your apps the next time they load Native Notify, and a removed one loses access on their next request.

• If they have a Native Notify account, they join at once and your apps appear in their Native Notify dashboard marked Shared, with their role.
• If they don't, the address is held as a pending invite. Native Notify sends no email. Tell them to register or log in with that exact address and the invite becomes a membership then. There's no acceptance step.

Roles

Role	Can do
Admin	Everything, including the two dangerous operations: deleting an app and changing an app's push credentials.
Developer (default)	Day-to-day use: send and schedule pushes, the inbox, subscribers, analytics, renaming apps.

A developer who tries a dangerous operation gets 403 in Native Notify and through MCP: "Only account admins can do that. Ask the account owner to make you an admin." A few more actions are admin-only: validating push credentials, rotating app keys and web-push keys, deleting a notification from every inbox and, from the agent chat, sending to all devices, turning on or changing an all-devices schedule or AI Push, or deleting an audience on a Classic app.

Plan limits

Plan	Team members
Free	Up to 10
Premium	Up to 1
Pro	Up to 3
Team	10 included, then $15/month per additional member

Members and pending invites count the same toward the limit. At the limit, adding a member or invite answers 403 with an upgrade message. Re-inviting a pending address only changes its role, so it's never refused. Team has no cap: each member beyond 10 is charged, prorated, when they join. See Plans & billing.

Moving to a plan with fewer team members never removes anyone. Your oldest members, up to the new limit, keep access. The rest stay on the team but see none of your apps, and show as No access — upgrade under Settings → Team Members in Native Notify. They get access back on their next request after you upgrade or remove members.

Change a role or remove a member

Change a role with the dropdown next to the member. Remove a member with the trash icon: they lose access on their next request, and you can add them back any time. Cancel a pending invite with its trash icon and that address won't join when it signs up. Adding the address again with the other role changes the pending role.

API

Team endpoints take a Native Notify dashboard session or an MCP access token. An app token is refused with 403. Only the account owner can call them, and ids outside the owner's team answer 404.

Call	MCP tool	Answers
GET /api/team/members	list_team_members, list_team_invites	members, memberships, invites, roles and seat_limits
POST /api/team/members { email, role? }	invite_team_member	201 { member }, or 201 { invite, pending: true } for an email with no account. 409 if already a member. 400 for your own account or an invalid email or role. 403 when the plan's limit is full (never on Team).
PATCH /api/team/members/:memberId { role }	update_team_member_role	201 { member }
DELETE /api/team/members/:memberId	remove_team_member	201 { removed: true, team_member_id }
DELETE /api/team/invites/:inviteId	cancel_team_invite	201 { removed: true, invite_id }

Each member and membership carries has_access, false while the owner's plan doesn't include them. seat_limits is { used, max, included, extra_member_cents, members, pending_invites, with_access }, with max null on Team.

For team members

When someone adds you, their apps appear in your Native Notify dashboard marked Shared, with your role. You use them like your own apps, subject to your role, and you don't manage that account's team.