Team

The Team page lists everyone who can get into your organization. From here you invite new people, resend an invite that hasn't been picked up, change someone's role, remove a member, or leave the organization yourself.

Who can do what

Everyone on your team has one of four roles, shown as a coloured badge next to their name:

• Owner (violet) — full run of the dashboard, including everything on this page.
• Admin (blue) — the same day-to-day access as an owner, everywhere in the dashboard. The differences are all on this page: admins can't hand out the Owner role, can't change anyone's role, and can't remove an owner.
• Sales (amber) — only exists in partner organizations. Someone with the sales role sees none of your organization itself — no Overview, Places, Banking, Payouts or Team — just the Clients section. Any other page sends them back there.
• Technician (teal) — only exists in partner organizations, and covered just below.

Sales members and technicians can't open the Team page at all — looking after the team is for owners and admins.

The technician role

A technician is the person who services machines — your own field engineer, or the one your partner sends. The role exists in partner organizations only, and it is deliberately narrow: "Technician — services the terminals of your clients".

What a technician gets:

• The Fleet page: every terminal of every client the partner looks after, and the workbench for one of them — settings, connection history, crash reports and maintenance notes. See Fleet.
• The Clients list, read-only, because that is how they find the business they were sent to. They cannot create a client, invite one, request access to an existing business, or cancel one.
• Nothing else of your own organization: no Overview, Places, Banking, Payouts or Team.

They also always have the advanced terminal controls switched on — restarting a machine and pushing firmware to it is the job, so there is no switch for them to find. See Basic and advanced controls.

To give someone the role, use Make technician on their row; the confirmation says "Change {email} to technician? They will only see your clients' terminals." Make admin moves them back.

What a technician may actually do to a client's machine is the client's decision, not yours — see Partner maintenance below.

Reading the members list

Each row gives you the person's Email, Role, Joined date, and Last sign-in date (an em dash if they've never signed in). Your own row has a little YOU tag on it.

Depending on your own role, you'll see actions on the right of each row: Resend invite, Make sales / Make admin, Make owner, Demote, and Remove — which reads Leave on your own row. Resend invite only appears if you can invite people yourself, and never on your own row.

Inviting someone

1. Press Invite user (top right). A panel titled "Invite a user" opens: "Add someone to this organization. Share the set-password link below so they can sign in."
2. Type their email address.
3. Pick a role: Admin (the default), Owner, Sales or Technician.
   • Owner only shows up if you're an owner yourself — admins see "Only owners can grant the owner role." and can choose the rest.
   • Sales and Technician only show up in partner organizations.
4. Leave Send invitation email ticked if you'd like us to email them ("We'll email them a link to verify their address and set a password.").
5. Press Send invite.

What happens next depends on whether they already use Citizen Pay.

They already have a Citizen Pay account

They're simply added to your organization and you'll see "User added". No email goes out — they sign in as usual and your organization turns up in their business switcher. There is no set-password link on this screen: they already have a password.

They're new to Citizen Pay

An account is created for them. You'll see "User invited" along with a set-password link and a Copy link button, so you can pass it on yourself if you'd rather. If you left the email box ticked, an invitation email goes out too and a green "Invitation email sent." confirms it.

That email is titled "Verify your email" and has a Verify email button. It's a one-time link that confirms their address, signs them in, and takes them to a page where they choose a password. Once they've set it, they land in your organization's dashboard with the role you picked. The email goes out in your dashboard language (English, French, or Dutch).

A few things worth knowing:

• Inviting someone who's already on the team shows "This user is already a member."
• We limit how fast invite emails go out. If that stops the email, the account is still created — you get the "couldn't be sent" message below, with the link to pass on yourself.
• Press Invite another on the result screen to move straight on to the next person.

Resending an invite

If someone hasn't signed in yet, their Last sign-in column shows an em dash and a Resend invite action appears on their row. Press it to send the same verify-email message again; a quick "Invite sent" confirms it went.

Once someone has signed in even once, we won't resend it ("This member has already signed in."). If they've forgotten their password, they should use Forgot password? on the sign-in page instead.

Changing someone's role

Only owners can change roles — admins see "Only owners can change roles." And nobody can change their own ("You cannot change your own role.").

Your options, each with a confirmation pop-up:

• Make owner — promote an admin to owner ("Make {email} an owner? They will have full control of this organization, including team and banking.").
• Demote — turn another owner into an admin ("Demote {email} to admin?").
• Make sales / Make technician / Make admin — in partner organizations only, move someone between Admin, Sales and Technician. The confirmation spells out what changes: sales members "will only see the clients section", technicians "will only see your clients' terminals", admins "will see the whole organization".

Make owner only appears on an admin's row: owners already own, and a sales member has to be made admin before they can be promoted — handing out ownership is always a deliberate second step.

Removing someone

Owners and admins can both remove admins and sales members: press Remove on their row and confirm "Remove {email} from this organization?".

Owners have extra protection:

• Admins can't remove owners ("Admins cannot remove owners.").
• Even an owner can't remove another owner outright — demote them to admin first ("Downgrade this owner to admin before removing them."), then remove them.

Removal happens the moment you confirm, and there's no undo. It only takes away their access to your organization — their Citizen Pay account carries on existing.

Leaving an organization

On your own row, the remove action reads Leave. Confirm "Leave this organization?" and you're taken back out to your other organizations. You stay signed in — it is only this organization you have left, and if you belong to another one the dashboard opens straight into it.

You can only leave if at least one other owner stays behind — otherwise you'll see "You can't leave — at least one other owner must remain on this organization." A sole owner can never leave the organization stranded, so invite another owner first.

Stopping with Citizen Pay altogether, rather than just leaving? Then the whole organization is closed instead — see Closing your organization.

Partner maintenance

If a Citizen Pay partner set up your account or looks after your machines, a Partner maintenance card sits at the bottom of this page: "Allow {partner} technicians to configure and service your terminals." Businesses with no partner never see it — there is nobody to grant anything to.

Leave it on and that partner's owners, admins and technicians can work on your terminals exactly as you can: rename them, change their settings, restart them, push firmware, read and write their maintenance notes. It is what lets someone fix a machine without you standing next to it.

With maintenance on, you also get a record of it: every change the partner makes to one of your terminals is written on that terminal as a maintenance note — what changed, who did it and when — which you read on the terminal's own Notes tab. See maintenance notes.

Turn it off and "your partner is left with status-only visibility on your terminals" — they can still see whether a machine is online, how it has been running, its firmware version and whether it has been crashing, so they can tell you to call someone. They can change nothing, and every control on their side goes read-only the moment you switch it.

Your own terminals are never affected: this is only about the partner. If the card cannot be read it says so rather than staying quiet — "Partner maintenance settings could not be loaded, so what your partner may do to your terminals is not shown here. Try again later." — because a blank space would read as "the partner has no access", which it is not.

If something goes wrong

Actions on this page report back in a red strip above the list. The ones worth recognising:

• "You can't leave — at least one other owner must remain on this organization." — you are the last owner. Invite or appoint another one first.
• "Admins cannot remove owners." — only an owner can act on an owner's row.
• "Downgrade this owner to admin before removing them." — demote first, then remove.
• "You cannot change your own role." — nobody edits their own row, whatever their role.
• "Only owners can change roles." — you are an admin; ask an owner.
• "The sales and technician roles are only available in partner organizations." — this organization isn't a partner, so there is no Clients section for a sales member to work in and no client fleet for a technician to service.

Emails are throttled to roughly one per address per minute. On Resend invite a second attempt too soon comes back with "Please wait a moment before requesting another email." — wait a minute and try again. On a fresh invite the limit shows up differently: the account is created either way, and you get the "couldn't be sent" message with the set-password link to share yourself.

If nobody is listed at all, the page shows "No team members."