Restrict column Edit and View Separately, and controlled by Person Column permissions

Feature requests
,
1

Development Workflow Requirements:

  • Need to control Edit and View access restrictions separately
  • Want to be able to indicate a person or team and most importantly indicate a person column from within that same board to control that access. If/when we break the access, the board should default to the most restrictive, i.e. to board owner(s) only and notify us in the same fashion as when we break a board automation by removing a column.

Somewhat recent and related posts I found searching, in case helpful:

2

Posting this reply again for visibility…

Heads up that this feature request is still a really big need for us!!! I recommend building out the permissions menu like this :backhand_index_pointing_down:

Right now the permissions settings menu looks like this…

image
image338×309 10.3 KB

So in practice, all you’d need to do is just put two tabs at the top for: viewing and editing. Then users could switch between those two tabs and control the permissions for individual members/guests very easily.

I’m also requesting support for the “people” column field to be an option in this menu, because right now you can only pick between teams and individual users, which is very tedious and not scalable. Using the “people” column field would allow a specific category of person (whoever is assigned in the column of the “people variable”) to be subject to the permissions in that column.

So in my situation, the actual use-case is that I have separate columns for different roles that each item needs: video editor, creator, project manager, and creative strategist. If this permissions menu could dynamically read the other column titles and dynamically call whichever person belongs to each column by it’s column name (as long as it’s a “people” column), then all we would need to do is pick the corresponding “people” column from the menu, and monday could set the view & edit permissions separately in the target column (the one we’re setting the permissions in). This makes it much easier to assign permissions to dymanic “roles” that we use columns to assign/manage.

I know this is an extra step, but the scope is pretty small since this would only need support for the people type column, since you can only actually assign people in terms of column values.

If you could also include support for “all members”, “all guests”, and “all viewers” as selectable options that appear in search, then that would be a really juicy bonus.

But anyway, just doing those first two things would solve almost all column permission needs in almost all use-cases at the same time at scale for almost all users. Just saying, this would be the most scalable way to do it imo.