Team Chat channel managers — open channel settings
Open the channel, click the ⋯ (More actions) button in the header and choose Channel settings — or right-click the channel in the sidebar and choose Edit channel. Before this, that entry appeared only for a workspace owner, an admin, or the person who created the channel. A channel manager — the role a workspace admin gives someone from the channel's Members panel — now sees it too, and can set slow mode there.
Who sees what
The dialog shows each person only what the server will actually accept from them:
| Setting | Owner / admin | Channel creator | Channel manager |
|---|---|---|---|
| Slow mode | Yes | Yes | Yes |
| Name | Yes | Yes | No — shown, not editable |
| Topic | Yes | Yes | No — shown, not editable |
| Public / private visibility | Yes | No | No |
| Who can post | Yes | No | No |
A manager opens the dialog with a short note saying why: the name, topic and visibility belong to a workspace admin. A plain member, or a member set to read-only, sees no Channel settings entry at all.
Why it is arranged this way
Hiding a control is a convenience; the server is what enforces it. The Firestore rules grant a
manager exactly one channel-settings write — slowModeSeconds — plus adding and removing people
from the channel. Everything else is refused at the server for a manager no matter what a client
sends, so the dialog is drawn to match those rules rather than to offer a switch that would fail.
Where the decision lives
- One pure helper decides both questions — who may open settings, and which fields each person may
change:
src/shared/team-chat/channel-settings-access.ts(canOpenChannelSettings,canEditChannelSetting). - The channel header, the sidebar's channel menu and the Edit Channel dialog all call it, so a change to the rule is made in one place.
- The role it needs is read once per channel, from the viewer's own channel member record, and only when the viewer is not already a workspace admin or the channel's creator.
What stays the same
- Alert routing, the AI switches and the webhook section keep their own gates: the AI switches stay creator-only, webhooks stay workspace-admin-only.
- Archiving and deleting a channel stay workspace-admin (or, for deleting, creator) actions where they already live.
Last verified 2026-11-21