Skip to main content
Bringing your team into Spotzee takes two role decisions. One at the organisation level (billing, projects, team management). One per project (campaigns, journeys, settings). Pick deliberately. Spotzee defaults to least-privilege.
Inviting at the organisation level requires the Owner or Admin organisation role. Adding someone to a specific project requires the project admin role (organisation owners and admins receive it automatically on every project).

​
The two role hierarchies

Spotzee keeps organisation roles and project roles separate. Both apply at the same time. A teammate’s project role governs their day-to-day work; their organisation role governs cross-project concerns like billing.
Three roles, narrowest to broadest:Hierarchy: member < admin < owner.

​
Invite someone to your organisation

Use this for someone who isn’t yet in your organisation. They’ll get an email with a sign-up link.
1

Open the Admins page

From the organisation menu, open Admins.
2

Start an invitation

Choose Add admin, then fill in the form:
  • Email address (required).
  • First name and Last name if you want them pre-filled on the new account.
  • Role. Pick member, admin, or owner based on the hierarchy above.
3

Send the invitation

Submit the form. The invitation lands in Pending Invitations. The invitee receives an email with a sign-up link. Once they accept, they move from Pending Invitations into the main Admins list.
Cancel a pending invitation any time from the Pending Invitations section before the invitee accepts.

​
Add someone to a project

Use this when the person is already in your organisation as a member but needs access to a specific project. Owners and admins are added to every project automatically and don’t need this step.
1

Open the project Team tab

Inside the project, open Settings and pick the Team tab.
2

Add a team member

Add a team member, then enter their email address and pick a project role from support, smtpproxy, editor, publisher, or admin.
3

Confirm

Confirm. They appear in the project team list with the role you assigned. Their organisation role stays as it was.

​
Change or remove access

Open the relevant team list. Admins at the organisation level for organisation access. Settings then Team inside a project for project access. Use the row’s overflow action to:
  • Edit their role. New permissions take effect on their next request.
  • Remove them. Removal at organisation level cascades across every project. Removal at project level affects that project only.

​
Picking the right role

A few rules of thumb:
  • Reserve owner for billing-responsible staff. The role can delete the organisation.
  • Grant organisation admin only to people who actively need to invite teammates or manage billing. Day-to-day operators don’t need it.
  • For project work, default to editor. Promote to publisher only for those you trust to push journeys live. Reserve project admin for people who configure providers, custom domains, and the project team.
  • support is the safest read-only level for customer-support staff. Use it when the alternative is over-granting editor.

​
Next steps

Set up a project

Configure project defaults: locale, timezone, tracking.

Concepts

Brush up on Users, Journeys, Segments, Channels, and Providers.

Quickstart

Send your first campaign in ten minutes.

Authentication

Read the API-key model before issuing your first key.