Skip to content

Board: UCLA events editor sign-in - #102

Merged
getvindicated2day merged 2 commits into
mainfrom
board-ucla-events
Oct 13, 2026
Merged

getvindicated2day merged 2 commits into
mainfrom
board-ucla-events

Conversation

@getvindicated2day

@getvindicated2day getvindicated2day commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

What this does

Adds an events editor sign-in for UCLA, the same as Berkeley's socials editor password.

  • New Railway variable BOARD_UCLA_EVENTS_PASSWORD. It's listed blank in .env.example; the value isn't in the code.
  • Signing in to /board/ucla with it gives the member view, plus adding, editing and deleting events (dates, times, locations, leads, status). Nothing else is editable, and admins-only content stays hidden (admins-only announcements, unassigned tasks, the Changes tab, email results).
  • The header says Signed in as events editor.
  • The server enforces it. Event writes accept only that chapter's admin or events-editor session. Every other write is admin-only, and sessions are per chapter, so Berkeley sessions can't touch UCLA.
  • The change log now labels each entry by who made it ("UCLA events editor", "UCLA admin", "Berkeley socials editor"). Before, every entry said "admin". The optional "Your name" box appears on the events tab for the events editor, and the log shows it as self-reported.
  • Admins keep everything they had.

This reuses the existing socials role, which UCLA's hub now calls the events editor.

Tested (local production build)

  • The events password added an event and set its location, time, lead and status, then deleted another. All four changes are logged as "UCLA events editor (Sahana, self-reported)".
  • The events password got 404 on member, assignment, announcement, meeting, settings, teams, restore, announcement email, new week, import, invite, photo upload and person-status writes.
  • UCLA member, Berkeley admin and Berkeley member sessions all got 404 adding, editing or deleting a UCLA event. The events cookie can't write to Berkeley.
  • As the events editor, no other tab shows edit controls, and there's no Changes tab. There's no sideways scrolling at phone or desktop width.
  • Typecheck, lint and build pass.

Deploy

Add BOARD_UCLA_EVENTS_PASSWORD in Railway with a value different from the other passwords, and give it to whoever runs UCLA's events.


Generated by Claude Code

- BOARD_UCLA_EVENTS_PASSWORD signs in to /board/ucla as the events
  editor (the socials role Berkeley already has): the member view plus
  adding, editing and deleting events. Event writes accept only that
  chapter's admin or events-editor session; everything else stays
  admin-only, and admins-only content stays hidden.
- The header says "Signed in as events editor".
- The change log labels each entry by the role that made it ("UCLA
  events editor", "UCLA admin"). The optional "Your name" box also shows
  on the events tab for the events editor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QzNDQSmhjgKE63rwUnwcMq
@getvindicated2day
getvindicated2day merged commit 23b2be1 into main Oct 13, 2026
1 check passed
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.

2 participants