Staff and Roles
Invite your team, give each person the right role, and remove access
Your team's access is managed by your Admin under Manage > Team & roles. The page lists who can sign in and what their roles let them change, with each person's Status (Invited, Active or Removed), when they were invited, and when they were Last active in the back office.
A person belongs to your organisation, not to one operator: if your organisation runs several operators, your staff see all of them.
Roles
| Role | In one line | What it can change |
|---|---|---|
| Admin | Everything, including setup and people | Everything Content and Support can, plus Manage: your operator's settings, each environment's setup, your embed's look, and your team |
| Content | Events, markets and what players see | Create, edit, publish, reschedule and archive your events and markets; your own categories; translations (writing, translating with AI and approving them) and images; enter results, hold, release, close and void your own events' markets; confirm Scout's answers and publish or reject its suggestions; Scout's settings; suspend and resume your book on platform events; Curation |
| Support | Players: look up, block and unblock | Block and unblock players |
| Finance | Money: reads trades and players' money | Nothing: reads Trades, Finance, Players, the Dashboard, the Queue and Events |
| Viewer | Reads everything, changes nothing | Nothing |
A person can hold more than one role. Each role shows the areas it needs (see Back Office Basics), and the back office refuses an action a person's roles do not allow. Whatever the role, your staff cannot change the fee schedule, the trading engine, your currencies or your operator's status: Phoenix sets those.
Give each person the narrowest role that lets them do their job.
Invite Someone
Only an Admin invites. Choose Invite, enter their Email, First name and Last name, pick their Roles, and Send invite.
- They get one email to set up their sign-in. Someone who already signs in gets access straight away.
- One email address belongs to one organisation. An address already used in another organisation cannot join yours: use another email for that person.
- Until they sign in they show as Invited. If the email went astray, use Resend invite on their row: a new email goes out with a fresh link.
Change Roles
Use Edit roles on a person's row. The change applies at once, and the person sees a message that their roles changed. You cannot take the Admin role from the last Admin who has signed in (see below).
Remove Someone
Use Remove on a person's row and confirm Remove access. Nobody is offered Remove on their own row: ask another Admin.
- Their access ends at once: a back office they have open stops working immediately, and they can no longer sign in. They see "Your access to this backoffice has ended".
- Their past actions stay in every history under their name.
To give a removed person access again, invite them again with their email. A person shown as Removed is not turned away by the invite form: the invite restores their access and works as for anyone new (see Invite Someone).
Your organisation always keeps an Admin who can sign in. The back office refuses to remove the last Admin who has signed in, and refuses to take the Admin role from them, saying that the organisation needs one: give someone else the Admin role first. Keep at least two Admins, so one can be away.