Atlas / tournament documentation

Users and roles

Who holds an admin, tab or compliance seat on a tournament, how seats are added, changed and removed, and who may manage them.

Users & Roles lists the people who hold a seat on one tournament and is where a seat is added, changed or removed. A seat is a named level of access to the tournament's admin console. Three seats exist: Admin, Tab and Compliance. People who administer the tournament through their role in the organization do not appear in the list, because the list shows seat rows only.

The screen is the Users & roles entry under Records in the left rail, at the route /tournaments/{id}/admin/users. Competitors, coaches and judges are not managed here. The screen ends with two tiles that point to the places where they are managed.

Who can use it

Opening the screen and managing seats are two different permissions.

Role	Can open the screen	Can add, change and remove seats
Platform admin	Yes.	Yes.
Organization owner or admin	Yes.	Yes, unless this tournament gives the same account a Tab seat. An owner or admin holding a Tab seat can read the list and cannot change it.
Admin seat	Yes.	No. The Admin seat runs the tournament but does not manage seats. Seats are managed by the organization's owner and admins.
Tab seat	Yes. The rail shows the entry under Records.	No.
Compliance seat	No. Sent to Records with a read only notice.	No.
Settings only role in the organization	No. Sent to the organization's admin page with an update notice.	No.
Anyone else	No. The route answers as not found.	No.

An account that cannot manage seats sees the heading, the introduction and the sentence Your organization's owner and admins manage seats. The list and the Add Seat form are left out. The same check runs again on the server for every add, change and removal, so a hidden control is not the only guard.

A tournament that belongs to no organization has only platform admins able to manage its seats.

The three seats

Seat	What it holds
Admin	Full access to this tournament. Announcements, fees, refunds, promo codes and waivers are included.
Tab	Runs the tournament: setup, rounds, ballots, check-in, standings, Finalize and Records. Fees, refunds, promo codes and announcements stay with full admins. The tab room is the group of staff who run pairings and results.
Compliance	Read only. Views Records and compliance reports and changes nothing. A compliance seat sees only those two screens.

The rail and the console draw the role from these rules. A platform admin is always a full admin. A person whose seat row says Tab is a tab seat. A person refused by the admin check but holding a Compliance seat is a compliance seat. Every other person who passes the admin check, including organization owners and admins and Admin seats, is a full admin.

Controls

Control	What it does	Default or limit
Administration	A small label above the heading.	Not editable.
Users & Roles	The heading, followed by the sentence Control who can administer and the tournament's name.	Not editable.
Tournament Administrators	The section that holds the list and the form. Its introduction says the Tab seat runs the tournament and that a Compliance seat reads Records and compliance reports and changes nothing.	Shown only to an account that can manage seats.
Seat row, email	The seat holder's email address, or No email when none is on file.	Rows are ordered by the date the seat was granted, oldest first.
Pending	A marker beside the address. It means the account has never signed in, so an invitation has not been accepted.	Absent when the sign in status cannot be read.
Seat row, detail line	The holder's name followed by Added and the date of the grant. The name is left out when it only repeats the part of the email before the at sign, which is what an invited account is named.	Date as year, month and day.
Seat select in a row	Changes that person's seat to Admin, Tab or Compliance. The change is made as soon as another option is chosen. No confirmation is asked.	Starts at the person's current seat. A row with no role reads Admin.
Remove	Removes the seat after a browser confirmation that reads Are you sure you want to remove this admin?	Removing a seat does not delete the account.
No co-admins configured.	The empty state when the tournament has no seat rows.	Not editable.
Role	A select in the form below the list. Chooses the seat that the new person receives.	Admin. Options: Admin, Tab, Compliance.
Invite by Email	The address of the person to add. Placeholder colleague@example.com. Required.	Surrounding spaces are removed and the address is read in lower case.
Add Seat	Adds the seat. The button reads Adding... while the request runs.	Disabled while a request runs and while the email field is empty. After a success the email clears and the Role returns to Admin.
Registrations tile	A link to registration management. Text: Manage competitor entries, teams, and registration details.	Opens the Field console's registrations view.
Judges tile	A link to judge management. Text: Manage judge profiles, availability, and assignments.	Opens the Field console's judges view.

How adding a seat works

The address is looked up. The address is matched against existing Meridian accounts.
An existing account receives the seat at once. No email is sent. The notice reads the address followed by now has the seat and the seat's name.
A new address gets an account made for it and an invitation link, and the invitation email is sent. The link sets a password and opens this tournament's console. The email subject names the tournament, and names the seat unless it is Admin. The email states what the seat can do and carries a button labeled Accept my invitation. The notice reads Invitation sent to the address for the seat. It shows as pending until they sign in.
The seat is granted either way. If the invitation email fails to send, the account and the seat already exist. The screen then reports the failure as an error, and the new row appears after the page is refreshed.
Records. Granting, changing and removing a seat each write an entry: Admin seat granted, Admin seat role changed and Admin seat removed. The entry names the person by account and never by the address typed.
A person can hold one seat per tournament. Adding an address that already holds a seat is refused. Change the existing seat in its row instead.

Last admin protections

The code has no rule that keeps at least one seat on a tournament, and no rule that stops a person from changing or removing the seat they hold themselves. Removing the last seat does not remove access for platform admins or for the organization's owners and admins, because that access comes from their role. Three rules do limit seats:

A seat never grants a role above its own. A Tab seat cannot add or change seats, even when its holder is also an organization owner or admin.
Only platform admins and organization owners and admins manage seats. The Admin seat does not.
A Compliance seat is read only at the database. Every write is refused for it, whatever the screen offers.

Tasks

To give a co-director a seat:

Open Records in the rail. Select Users & roles.
Choose the seat in the Role select.
Type the person's email address in Invite by Email.
Select Add Seat. Read the notice under the form.
Tell a person who received an invitation to open it from the email. Their row shows Pending until they sign in once.

To change a seat, open Users & roles and choose another option in the seat select on that person's row. The page refreshes with the new seat.

To remove a seat:

Open Users & roles.
Select Remove on the person's row.
Confirm the browser question.

Troubleshooting

Message	What it means	What to do
Your organization's owner and admins manage seats.	The signed in account cannot manage seats.	Ask an organization owner or admin, or a platform admin.
Access details could not be loaded completely. Refresh the page before changing permissions.	One of the reads for the list failed, so the list may be partial.	Reload the page before changing a seat.
Choose a valid email address and admin role.	The address was empty or the seat was not Admin, Tab or Compliance.	Fill the address and choose one of the three seats.
Unauthorized	The account may not manage seats, or the tournament does not belong to the organization the page was opened under.	Use an owner or admin account of the tournament's organization.
Could not check your admin access. Try again.	The permission check could not run.	Try again.
The tournament could not be read: followed by a reason	The tournament row could not be read.	Reload and try again.
That address could not be looked up: followed by a reason	The account lookup failed. Inviting would risk a second account for an address that already has one.	Try again.
Could not invite that email address.	The invitation link could not be made. A more specific reason replaces this sentence when one is available.	Check the address and try again.
That user is already an admin for this tournament.	The account already holds a seat on this tournament.	Change the seat in its row.
Failed to add admin. followed by a reason	The database refused the grant.	Read the reason and try again.
The admin was added, but the invitation email did not send, followed by the reason	The seat and the account exist. The invitation mail did not go.	Refresh the page. The row shows Pending. Send the person the sign in address directly, or remove the seat and add it again.
Invitation sent to an address for the seat of the chosen name. It shows as pending until they sign in.	The success notice for a new address.	None.
An address followed by now has the seat of the chosen name.	The success notice for an existing account.	None.
Are you sure you want to remove this admin?	The confirmation before a removal.	Confirm or cancel.
Failed to remove admin.	The database refused the removal.	Try again.
That admin assignment was not found.	The seat row no longer exists, for example because another admin removed it.	Refresh the page.
You do not have permission to delegate tournament access.	A database rule refused the change. It appears in a browser alert after a change in the seat select.	Use an account that manages seats.
Invalid tournament admin role.	The seat was not one of the three.	Choose a listed seat.
That account does not exist.	The account behind the seat could not be found.	Add the person again with their email address.

A failed seat change shows the message in a browser alert and the select keeps showing the saved seat. A failed removal also shows an alert.

Related pages: Roles and permissions for what each seat reaches across the console, Organization and account for organization roles, and Announce for the full admin only screen.