Skip to content
sendou.ink docs

Tournament organization · Permissions

2 modules · 2 exports · 1 repository · 5 e2e tests · 4 routes

Who may do what in Tournament organization: the per-object permissions it builds with every place checking them, and the checks in its code. See Permissions for how authorization works and the reference for every role and feature.

Granted here

Built at read time into what the functions return, a list of the user ids holding each permission. Checks are listed wherever they are, other features' included.

PermissionGranted byChecked in
EDIT
findBySlug
orgAdminUserIds = organization.members
	.filter((member) => member.role === "ADMIN")
	.map((member) => member.id)
Serverorg.$slug.edit.server.tsorg.$slug.edit.server.tsorg.$slug.stats.server.ts
Clientorg.$slug.tsx
BAN
findBySlug
orgAdminUserIds = organization.members
	.filter((member) => member.role === "ADMIN")
	.map((member) => member.id)
Serverorg.$slug.server.ts ×2
Clientorg.$slug.tsx
read directly org.$slug.server.ts

Global roles

The global roles this feature's code checks, see who has each.

RoleChecked in
ADMIN
Serverorg.$slug.server.ts ×2
Clientorg.$slug.tsx
TOURNAMENT_ADDER
Serverorg.new.server.ts
Clientorg.new.tsx

Outside the system

Reading x.permissions.NAME directly skips hasPermission and with it the admin bypass, and authorizing an action on an object with isAdmin and friends is a bug. Some of these are deliberate, the permissions doc lists the boundaries.