Skip to content

feat(events): per-event coordinator role (#530)#562

Open
adrianbp2 wants to merge 1 commit into
OxfordRSE:mainfrom
adrianbp2:feat/event-coordinator-role
Open

feat(events): per-event coordinator role (#530)#562
adrianbp2 wants to merge 1 commit into
OxfordRSE:mainfrom
adrianbp2:feat/event-coordinator-role

Conversation

@adrianbp2

Copy link
Copy Markdown

Summary

Implements #530: a per-event coordinator role so an admin can let someone edit a single event without granting global admin rights.

Changes

  • EventStatus.COORDINATOR enum value + migration
  • lib/eventAccess.ts helper (admin || coordinator)
  • Authorize coordinators on event edit (PUT /api/event/[id]), event group edit/delete, and event user management
  • Admin-only kept for: deleting an event, creating events, and granting the COORDINATOR role
  • UI: edit tab shown to coordinators; coordinator option in the user role selector visible to admins only

Testing

  • New cypress/e2e/event-coordinator.cy.js (4 cases) — passing locally against a test DB
  • tsc --noEmit clean, Prettier clean
  • Manual UI check: admin assigns coordinator; coordinator can edit but cannot delete the event or promote others

Closes #530

Coordinators can edit a single event without global admin rights.

- EventStatus.COORDINATOR enum + migration
- lib/eventAccess helper (admin || coordinator)
- gate event/eventGroup edit and event user management on coordinator
- DELETE event and granting COORDINATOR stay admin-only
- UI: edit tab for coordinators + coordinator option for admins
- e2e test for coordinator permissions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Admin rights limited to a single event

1 participant