Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support "support" stream type with topic-specific permissions #5839

Open
alya opened this issue Mar 6, 2024 · 0 comments
Open

Support "support" stream type with topic-specific permissions #5839

alya opened this issue Mar 6, 2024 · 0 comments
Labels
webapp parity Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity.

Comments

@alya
Copy link
Collaborator

alya commented Mar 6, 2024

In zulip/zulip#19434, we plan to make it possible to restrict which topics in a stream a user can view and send messages to. Users with restricted permissions:

a. Can start a new topic, and have regular permissions for that topic (read, post, etc.).
b. Cannot view or send messages in other topics.
c. Only see their own topics in auto-complete suggestions in the compose box.
d. Get an error if trying to send to somebody else's topic. It's probably OK that this leaks information about what other topics exist.

We should make sure the mobile apps can support these restrictions.

Web app / server issue:

@alya alya added the webapp parity Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity. label Mar 6, 2024
@gnprice gnprice added the server release goal Things we should try to coordinate with a major Zulip Server release. label Jun 25, 2024
@alya alya removed the server release goal Things we should try to coordinate with a major Zulip Server release. label Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
webapp parity Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity.
Projects
Status: No status
Development

No branches or pull requests

2 participants