Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Document owner | |
---|---|
Designer | |
Tech lead | |
Technical writers | |
QA | |
OKR | Improve Team/Channel Administration |
Product Board | |
Request (CR) | |
Request (other) | |
Design Spec | |
Technical Spec | |
Test Plan | |
Documentation |
Objective
By adding business value in the form of channel restrictions we enable new use cases that are in high demand from customers and enable growth. This feature also enables the highly requested “Read Only/Announcement Channels” toggle and we expect this to substantially advance user expansion for enterprise customers.
...
Topic specific announcement channels with specified members (e.g. public, employees, specific team or department, guest users, etc)
Technical event data channels where only bots can post information
Completely locked down channel without interaction from guests or membersRead-only channels where specific members are elevated to channel admins and can share important announcements with the rest of the team
Channels where members can post, reply, and react while letting guest accounts read and react only
Disabling channel mentions (e.g, @channel, @here, and @all) on very large channels to prevent users from alerting and notifying all other users at once
Locking down members in a channel by only allowing the channel admin to add or remove users
Assumptions
Leverages existing permissions architecture
UX should be simplified for managing this explicit permission change
...