Your team
Who can sign in to your business unit, and what each of them may do. Every person gets their own sign-in and a role that covers only the parts of the console they need.
📷 Screenshot placeholder — Team → Team members, the seats table with the invite panel open.
Team is where you bring people into your business unit and hand them work. Instead of sharing one login, each person signs in with their own email and password and holds a seat with a role. The role decides which areas of the console they can see and change; a project scope can narrow that to the projects they look after.
Who is on the team
- The Owner — the account that created the business unit. It has full control, its seat cannot be changed or removed, and the Owner role cannot be given to anyone else.
- Admins — other accounts that manage the whole business unit. Owners and admins pass every permission check; roles are what limit everyone else.
- Members — the people you invite. Each holds one role and, optionally, a project scope.
Every seat appears in the table with its role, project scope, status and who invited it.
The roles you start with
| Role | What it covers |
|---|---|
| Owner | Everything. A system role — never offered in the pickers. |
| Admin | Projects, people and this business unit, with read access to billing. The one built-in role you can edit. |
| Community | Forum moderation, plus read access to farmers, network, reports and alerts. Locked. |
| Finance | Revenue, withdrawals, fees, commissions and billing, plus read access to reports, claims and farmers. Locked. |
A locked role cannot be edited, but you can duplicate it and shape the copy. Custom roles are yours to build from scratch — see Building a role.
Inviting someone
- Open Team and fill in the invite panel: their work email, a role and, if you want, a project scope.
- Send it. They receive an email link that is valid for seven days.
- They sign in — or sign up first — with that same email and accept. The seat becomes active with the role and scope you chose.
The invite is tied to the address you typed: an account signed in with a different email cannot accept it. Someone who already holds a live seat cannot be invited again.
Pending invites appear in the table as Invited. Resend sends a fresh email and restarts the seven days — an expired invite can be resent too. Revoke cancels it.
📷 Screenshot placeholder — a pending invite row with Resend and Revoke.
Seats and your plan
Your plan sets how many seats the business unit includes. The Team page shows seats used against that allowance. Active members and pending invites both count; removed members do not.
Changing or removing a member
Open a seat to change its role or project scope; the change applies to everything they do from then on. Remove from team ends their access straight away — a removed person keeps no permissions. If they come back, invite them again; accepting restores the seat.
Nothing you do here touches the Owner's seat.
What a role controls
A role is a list of resources — projects, tasks, entries, claims, bonus offers, revenue, withdrawals, forum boards, the team itself and more — and, for each, which of create, read, update and delete it may do. Any write includes read.
Grants on project resources can be narrowed to one project, and grants on forum resources to one board. A seat's own project scope goes further: it limits every page the seat touches — farmers, entries, forum threads — to that project.
Two things to keep in mind:
- Team & roles is the grant that lets a member change the team, including their own access. Give it only to people you would trust with an Owner invite.
- Owners and admins are not limited by roles at all.
For the full grid and how scoping works, read Building a role.