Managing a Channel Members, roles, who may post, and how to retire a channel properly.

Channel settings has four tabs, and they escalate in consequence from left to right.

About

The name, icon, topic and description.

The description is worth writing. It is what somebody reads when deciding whether to join, and a channel with no description gets either everybody or nobody.

Members

Who is in, with their role, and the controls to add, remove, promote and demote.

Three roles:

Role	Can
Owner	Everything, including transferring ownership and archiving
Admin	Manage members and permissions
Member	Take part

Transferring ownership is owner-only, and it is the one to remember when somebody leaves. A channel whose owner has left the company is a channel nobody can archive.

Permissions

Three gates, available to admins and above:

Who can post. Restricting this turns a channel into an announcement feed. Right for a company-wide notice board, wrong for almost everything else.

Who can mention everyone. Worth restricting in any large channel. An @everyone to four hundred people should be a deliberate act.

Who can invite. Loose is usually correct; the exception is a channel scoped to a customer or a sensitive project.

Danger

Archive, which is owner-only, and leave, which anyone can do.

Archive rather than delete. The conversation stays findable in search, which matters more than tidiness the first time somebody asks why a decision was made two years ago.

Retire channels more often than feels comfortable. A workspace where half the channels are dead teaches people that channels are not worth reading, and that habit is difficult to reverse.

Notifications are not here

Your own notification setting for a channel lives in the channel header, not in this modal.

That separation is deliberate: this modal is for decisions affecting everybody, and how loudly a room pings you is nobody else's business.