Permission management for channel members

[abrhamgg]

Motivation

Teams often use channels as collaborative workspaces where members continuously update shared content based on project progress. However, channel canvases are currently only accessible to the person who created them, which creates friction when multiple team members need to contribute, review, or maintain the same canvas.

This becomes a problem for teams managing ongoing projects, documentation, planning boards, or shared notes, where ownership belongs to the team rather than a single individual.

Proposed solution

Introduce a permission system for channel canvases that allows channel owners or administrators to control access levels for individual members.

Possible permission levels could include:

• Owner: Full access, including managing permissions and deleting the canvas.
• Editor: Can create, edit, and update canvas content.
• Commenter: Can leave comments and suggestions without modifying the content.
• Viewer: Read-only access.

Additionally, channel administrators should be able to:

• Grant or revoke access for specific members.
• Transfer canvas ownership.
• Define default permissions for all channel members.
• Restrict sensitive canvases to selected users.

This would enable teams to collaborate more effectively while maintaining control over important content.

Alternatives considered

• Creating separate canvases for each contributor, which fragments information and makes collaboration difficult.
• Sharing credentials or relying on the original creator to make all updates, which does not scale well for active teams.
• Making all canvases public to the channel, which may not be appropriate for sensitive information.

Additional context

Many teams use channel canvases as living documents that evolve throughout a project's lifecycle. A granular permission system would allow teams to collaborate in real time while ensuring that access can be managed appropriately.

Before opening: none found.