Repository navigation
Atom 15.6.0
Limits even admins have: every /admin/* route that writes or grants access checks the role, deactivation and permission against the database on each call and is rate limited (60 a minute; user and object delete keep their own); user_check_permission gains a realtime mode. Audit columns (new config_column_audit_blocked) are refused in admin create, update and CSV import, and imported rows get the importing admin as created_by_id. /admin/postgres-query-runner-write takes one INSERT, UPDATE or DELETE, the last two with a WHERE (schema changes go through config_postgres, PgWeb for anything else). No user changes their own role, permissions or deactivation through the admin or permission routes. Nothing to change in projects, unless a project's own config_api overrides an /admin/* entry: give it the same checks.