Workspace settings
Team name, workspace notification switches, governance and the audit feed.
Workspace settings
/dashboard/team/settings is the workspace-level counterpart to /dashboard/settings (which is personal). It is gated to admin and super-admin roles.
What you can change
- Team name: up to 120 characters, trimmed, blanks rejected.
- Notification switches: five workspace-level toggles decide whether an event creates a notification at all — memberJoined, memberRemoved, profileUpdated, roleChanged and wellbeingAlert. Turning one off suppresses that notification type for everyone; it does not change what any individual sees in their own bell preferences.
- Member roles: change a role from the member table. Every change is recorded.
How the settings row works
The workspace has a single settings row. GET /api/team/settings creates it on first read with the documented defaults, so there is nothing to initialise by hand. PUT /api/team/settings accepts a partial object; unknown keys are dropped, booleans are coerced, and the response includes the name of the user who last updated it plus an ISO timestamp.
Audit feed
The page shows the most recent role changes with actor, previous role, new role and when it happened. The same data is available from the settings payload, so a script can diff it.
Relationship to personal preferences
- Workspace switches decide whether an event is recorded at all.
- Personal notification preferences in /dashboard/settings decide which recorded events reach your bell.
- The SSE feed at /api/notifications/live delivers whatever survives both filters.
Guarding it
- GET requires a session.
- PUT and role changes require a privileged role; everyone else gets 403.
- Writes create a notification for the affected members when the matching workspace switch is on.