I’m a Monday user, on EnterprisePlan, and just recently got the ‘upgraded Roles’ roll-out - which allows us to have more specific user-roles (Owner - Contributor - A Contributor - Viewer).
For the last one, having our main interest, as we would like to have users that can only View and Comment on items.
However, I’m now facing the following issue, which I already discussed with live-chat support, and they confirmed that is the case:
We have a user, which we gave a View-license on account-level**.** Then added this user as a Viewer on Workspace and Board-level. Which SHOULD (atleast what we thought) allow this user to ATLEAST be able to VIEW (which he can) but also COMMENT on items (which is not the case).
Which would now mean we have to give this user a full member license, to then restrict he’s capabilities again to View (and comment) only…? As the view-licence on user level is still restricting this person from being able to make comments on items…
This does not really make sense to me…
Thoughts? Advise? Solutions?
I did check all levels/checkboxes for permissions on Workspace-level, Board-level, …
Possible solution from live-chat was to create a GUEST-account, share Board(s) with them as a Guest. Which would then give Guest similar rights as members. However we will also have internal-people (with our domain-mailadresses) we want to give this level of access, so this is not really an options.
You are not missing anything and your understanding is correct. With the upgraded roles model the View license at the account level is intentionally read only. Even if the user is added as a Viewer at workspace or board level the account level View license still blocks commenting. That is why support confirmed what you are seeing.
Right now there is no way to combine a View license with comment permissions. Commenting is treated as an edit level interaction and requires a paid member license regardless of how restrictive the workspace or board role is set.
This unfortunately leads to the exact situation you describe where you would need to assign a full member license and then restrict the user back down to Viewer just to allow comments. From a cost and design perspective this feels counterintuitive but it is currently how the permission hierarchy works.
Guest access does allow comments with lower cost but as you mentioned it breaks down when you want to give this access to internal users on your own domain and at scale.
At the moment the realistic options are to use full member licenses with Viewer role for internal view and comment users or use Guest access where possible for external collaborators or accept view only users without comments. Many teams are giving the same feedback and requesting a View plus Comment license tier so this is worth formally submitting as a product feedback request if you have not already.
You are not configuring anything incorrectly. It is a product limitation rather than a setup issue.
Dr. Tanvi Sachar
Monday Certified Partner, Monday Wizard