docs(e2e): require admin role for the E2E account (PMS-155) #140

Merged

nrupard merged 1 commit from docs/pms-155-e2e-admin-account into main

2026-06-09 17:12:22 +02:00

nrupard commented

2026-06-09 17:10:53 +02:00

Owner

What

Documents the admin role as a hard requirement for the E2E account, in the staging provisioning step.

Why

The first staging run of the PMS-155 module specs (merged in #136) 403'd on all 14: the E2E account lacked the admin role. The suite enables tenant-gated modules via the admin-only PUT /api/v1/settings/modules/{module} route, and many writes are gated by RequireAdmin / RequireManager / RequireFinance (admin satisfies all three). A non-admin account passes only the tickets / contacts / OIDC / tenant-read specs and 403s on everything else. The README provisioning step previously said only "permission to manage tickets, companies, and contacts", which under-specified the role.

No code change: lib/factories.enableModule already surfaces the 403 with a clear message rather than swallowing it (the intended fail-loud behavior). Elevating E2E_EMAIL to admin/super_admin on the staging tenant unblocks the full suite.

🤖 Generated with Claude Code

## What Documents the `admin` role as a hard requirement for the E2E account, in the staging provisioning step. ## Why The first staging run of the PMS-155 module specs (merged in #136) 403'd on all 14: the E2E account lacked the admin role. The suite enables tenant-gated modules via the admin-only `PUT /api/v1/settings/modules/{module}` route, and many writes are gated by `RequireAdmin` / `RequireManager` / `RequireFinance` (admin satisfies all three). A non-admin account passes only the tickets / contacts / OIDC / tenant-read specs and 403s on everything else. The README provisioning step previously said only "permission to manage tickets, companies, and contacts", which under-specified the role. No code change: `lib/factories.enableModule` already surfaces the 403 with a clear message rather than swallowing it (the intended fail-loud behavior). Elevating `E2E_EMAIL` to admin/super_admin on the staging tenant unblocks the full suite. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

nrupard added 1 commit

2026-06-09 17:10:53 +02:00

docs(e2e): require admin role for the E2E account (PMS-155)

E2E (staging) / Playwright against staging (pull_request) Failing after 55s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

Check / fmt + clippy + compile + tests (pull_request) Successful in 1m43s

Details

e025056c38

The first staging run of the new module specs 403'd on all 14: the E2E account lacked the admin role, so the admin-only PUT /settings/modules/{module} enable call and the RequireAdmin-gated writes (sla/notifications/settings/audit) were all rejected. Only the non-admin specs (tickets, contacts, OIDC, tenant read) passed.

Document admin as a hard requirement in the provisioning step so the account is created correctly. No code change: lib/factories.enableModule already surfaces the 403 with a clear message rather than swallowing it, which is the intended fail-loud behavior. Elevating E2E_EMAIL to admin/super_admin on the staging tenant unblocks the full suite.

#PMS-155

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>