18
Not supported for the current status
VOTE
Status
Backlog
Categories
Conversation/inbox permissions
Created by
Guest
Created on
Mar 25, 2021
RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit PRD-I-4950 Introduce a view-only license type.
Support view-only inbox access and per-inbox permissions
Merged
Problem
Conversation permissions (reply, comment, assign, archive, etc.) can only be configured at the workspace level. Creating a separate workspace just to restrict actions on one or two inboxes is excessive and causes side effects.
Request
Allow conversation permissions to be defined per inbox. The primary use case is view-only inbox access — letting teammates see conversations without being able to reply, comment, or take actions. Additional per-inbox permissions could restrict send, assign, archive, and delete actions independently.
Yes! Uncertain if this is still true, but I attempted to do something similar a year ago where "view-only" users couldn't archive messages in team inboxes that weren't theirs. Only the team members for that inbox could do archive a message. What actually happened was that they could no longer archive messages even as a participant - they would never be allowed to reach inbox zero.