Admin · Permissions

0 modules · 0 exports · 3 repositories · 5 e2e tests · 2 routes

Who may do what in Admin: 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.

Global roles

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

Role	Checked in
`ADMIN`	Serveradmin.server.ts ×4 admin.streams.server.ts admin.streams.server.ts Clientadmin.tsx
`DEV`	Clientadmin.tsx
`STAFF`	Serveradmin.server.ts ×7 Clientadmin.tsx ×2

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.

isAdmin in app/features/admin/loaders/admin.server.ts:21 if (!isAdmin(userToCheck) && !isStaff(userToCheck) && !isDev(userToCheck)) {
isStaff in app/features/admin/loaders/admin.server.ts:21 if (!isAdmin(userToCheck) && !isStaff(userToCheck) && !isDev(userToCheck)) {
isDev in app/features/admin/loaders/admin.server.ts:21 if (!isAdmin(userToCheck) && !isStaff(userToCheck) && !isDev(userToCheck)) {