Organizations, members and permissions
How to invite your working team, what each role can do and how to keep different clients' competitions apart.
The organization is Torneyo’s unit of ownership. Tournaments, teams, athletes and referees belong to it — not to your personal account. That’s what lets you share the workload without sharing a password.
Why this matters
Without organizations, every tournament would be tied to one login. If that person went away, nobody would enter the weekend’s results.
With an organization, you invite whoever you need and each person signs in with their own account. Who joined, when, and what they changed is all on record.
Inviting members
Under Organization → Members, use Invite. Enter the email address and the person gets a link.
If they don’t have a Torneyo account yet, they create one on the spot and join the organization straight away. If they do, the invitation appears when they sign in.
A pending invitation can be cancelled at any time.
What each role can do
Each member joins the organization with a role, chosen in the invitation and changeable later. There are five, from most to least powerful:
- Owner — the organization’s owner. There is only one, and they can do everything, including handing ownership to someone else.
- Administrator — can do everything except deactivate the organization, transfer ownership and request the full data export.
- Manager — runs the day-to-day: tournaments, academies, classes, calendar and communication.
- Operator — works on the pitch and the court: match sheet, results, attendance and enrolments.
- Finance — follows billing and reports; in the operational areas, read-only.
| Action | Owner | Administrator | Manager | Operator | Finance |
|---|---|---|---|---|---|
| Deactivate the organization and transfer ownership | ✓ | – | – | – | – |
| Full data export | ✓ | – | – | – | – |
| Subscribe, change or cancel the plan; change how fees and bookings are paid | ✓ | ✓ | – | – | – |
| Invite, remove and change the role of members | ✓ | ✓ | – | – | – |
| Organization details, logo, colours and domain | ✓ | ✓ | – | – | – |
| AI settings and API keys | ✓ | ✓ | – | – | – |
| Create academies and classes | ✓ | ✓ | ✓ | – | – |
| Communication center and Athlete Grant | ✓ | ✓ | ✓ | – | – |
| Enter goals, cards and results | ✓ | ✓ | ✓ | ✓ | – |
| Enrol students, take attendance and assessments | ✓ | ✓ | ✓ | ✓ | – |
| Create events in the institutional calendar | ✓ | ✓ | ✓ | ✓ | – |
| View academies, classes, students, attendance and calendar | ✓ | ✓ | ✓ | ✓ | ✓ |
Nobody manages someone above them: an administrator manages managers, operators and finance members, but not another administrator or the owner.
The inventory module has its own permission table — see Inventory: equipment, loans and suppliers.
Warning Some screens still show buttons your role cannot use. In that case the action is refused on save with a permission notice — nothing is changed.
Working with more than one organization
One account can belong to several organizations. The selector at the top of the screen switches context, and everything you see becomes that organization’s.
Two common situations:
- You organize for different clients — one organization per client. Data stays isolated and each client can have its own members.
- You’re invited as a collaborator — you appear as a member in someone else’s organization, without mixing it with yours.
Warning Before creating a tournament or registering a team, check which organization is active in the selector. Creating in the wrong place is the most common slip, and moving things afterwards is a chore.
Access to tournaments
Access is additive: you can see a tournament if you’re a system administrator, or a member of the owning organization, or its creator. Any one condition is enough.
In practice: a member invited today already sees all of the organization’s earlier tournaments, without being added to each one.
Registrations from outside teams
When someone enters a team in your tournament, handling depends on where it comes from:
- Team from your organization — approved automatically.
- Team from another organization — joins the approval queue.
That keeps the tournament open to outside entrants without giving up control over who gets in.
Removing a member
Removing cuts off access immediately, but deletes nothing the person created. Tournaments, teams and results stay with the organization.