docs(e2e): spell out how to set the E2E account's admin role (SQL + bootstrap) #143

Merged

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

2026-06-09 18:31:48 +02:00

nrupard commented

2026-06-09 18:31:34 +02:00

Owner

Expand the provisioning step with the exact mechanism. The E2E account reaches mokosh on the bunyip Resource-Server path (ensure_user_from_bunyip), which resolves the request role from the mokosh users table row, not from the access token; the row is auto-created with the default role = 'technician'. Document the direct-DB UPDATE to flip it to admin, the admin-API alternative (PUT /api/v1/users/{id}), and the OAUTH_SUPER_ADMIN_EMAILS Google-path bootstrap for the first admin (noting it does not apply to the bunyip SSO path the E2E account uses).

#PMS-155

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

Expand the provisioning step with the exact mechanism. The E2E account reaches mokosh on the bunyip Resource-Server path (ensure_user_from_bunyip), which resolves the request role from the mokosh `users` table row, not from the access token; the row is auto-created with the default `role = 'technician'`. Document the direct-DB UPDATE to flip it to `admin`, the admin-API alternative (PUT /api/v1/users/{id}), and the OAUTH_SUPER_ADMIN_EMAILS Google-path bootstrap for the first admin (noting it does not apply to the bunyip SSO path the E2E account uses). #PMS-155 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

nrupard added 1 commit

2026-06-09 18:31:35 +02:00

docs(e2e): spell out how to set the E2E account's admin role (SQL + bootstrap)

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

Details

E2E (staging) / Playwright against staging (pull_request) Has been cancelled

Details

Check / fmt + clippy + compile + tests (pull_request) Has been cancelled

Details

abd36b9c91

Expand the provisioning step with the exact mechanism. The E2E account reaches mokosh on the bunyip Resource-Server path (ensure_user_from_bunyip), which resolves the request role from the mokosh `users` table row, not from the access token; the row is auto-created with the default `role = 'technician'`. Document the direct-DB UPDATE to flip it to `admin`, the admin-API alternative (PUT /api/v1/users/{id}), and the OAUTH_SUPER_ADMIN_EMAILS Google-path bootstrap for the first admin (noting it does not apply to the bunyip SSO path the E2E account uses).

#PMS-155

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