| Page Properties | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Document owner | |
|---|---|
Designer | |
Tech lead | |
Technical writers | |
QA |
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.
...
Both the “Member add/remove restriction” and the “Channel Mention restriction” derived from customer interviews and internal discussions about “nice-to-haves” regarding channel restrictions
This is a high-impact feature for some very large customers
Success metrics
Goal | Metric |
|---|---|
Solve channel moderation use-cases demanded by customers
| At least 50% of customers requesting “Read Only Channels” in in CR-9 confirm that this meets their basic expectations (must-have requirements). |
Handle a large number of users in the channel at the same time without performance issue | A read only channel (where only channel admins and above can post) can handle at least 1000 concurrent active users without a measureable performance impact. |
...