Support the read-only calendar role, show "Vorstand", fix link buttons
- Read-only role: /admin/me's permissions decide via canEditCalendar (lib/permissions.ts, mirrors the API's canWrite: only `access` writes). Read-only accounts see everything but get no "Neuer Termin", no "+", no "Veröffentlichen"; an event opens as "Termin ansehen" with locked fields. A "Nur lesen" badge in the header explains why. The API refuses their writes regardless. - The management calendar is labelled "Vorstand"; the slug stays `management` for the API, URLs and iCal links. - The subscription dialog's Apple/Google links are plain anchors styled with buttonVariants instead of Base UI Buttons rendering an <a>, which warned in dev and would have given them role="button". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
16 files changed
+155
-32
No files matched your search
@@ -15,6 +15,12 @@ What the calendar app does, as of the Next.js rewrite (September 2026).
|
||||
Sign-in happens in the admin app (one account for all Nachklang apps). Accounts need the calendar
|
||||
permission; without it the page says so instead of redirecting.
|
||||
|
||||
**Two levels** (granted in the admin app): *Vollzugriff* (`access`) can do everything below;
|
||||
*Nur lesen* (`read`, since 2026-11-08 in this app) sees every calendar, draft and subscription link
|
||||
but changes nothing - no "Neuer Termin", no "+", no "Veröffentlichen", and opening an event shows
|
||||
"Termin ansehen" with locked fields and only "Schließen". A "Nur lesen" badge in the header says
|
||||
why. The API refuses read-only writes anyway (403); the UI just doesn't offer them.
|
||||
|
||||
**List**
|
||||
- All calendars in one list, grouped by month, colour-coded per calendar.
|
||||
- Calendar chips toggle calendars on and off, with a count each; Geburtstage is off by default.
|
||||
|
||||
Reference in new issue
Block a user