Repository navigation
Conversation
The backend's central audit log and the admin dashboard page that shows it check `audit:read`, which no environment defined, so only Master Admin could open it. Seed it with the rest of the migration catalog so it can be given to a role. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. WalkthroughThis change adds an unmanaged ChangesAudit Read Permission
Change: Feature Merge Risk:
|
Main added 0023_role_people_binding, so the audit:read migration moves to 0024. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…mission # Conflicts: # drizzle/meta/0024_snapshot.json # drizzle/meta/_journal.json
Summary
0023_audit_read_permission, which seedsaudit:read("Read the audit log") the same way0016seeds the rest of the migration catalog: an ordinary permission (managed = false), no role granted,ON CONFLICT (key) DO NOTHING.0022's: the schema is unchanged.Why
The central audit log (PoliNetworkOrg/backend#90) and its dashboard page (PoliNetworkOrg/admin#123) check
audit:read, but no environment defines it. Master Admin's wildcard only covers permissions that exist in the catalog (resolveAccessinsrc/auth/rbac.ts), so today nobody can open the page, not even Master Admin, and it can't be given to any role.Test plan
drizzle-kit migrateon a local DB: the permission is createddrizzle-kit checkvp check,vp test🤖 Generated with Claude Code