Permissions - entities vs views

[Chr1sG]

@Eren_Turgut

1. create a view, filter it for employee XY, choose which fields are visible
2. then FIX that view such that it cannot be changed by whoever it is shared with
3. then assign groups or people to that particular view with access and edit rights ON A FIELD BASIS (e.g. Person A can edit field nr. 4, or even better, Person A can change field nr. 4 from A to B, but not from A to C)
4. at last, hide that view from my own dashboard i.e. like you can hide and show fields within entitites

1. possible

2. possible

3. not possible.
   you can set permissions for some users to be able view (but not configure) a particular space (and thus its views), and for some users to configure a space (and its views), but configuration at the field level is not possible. I do not anticipate field level access control will be coming any time soon.

4. if you’re an Admin, nothing can be hidden from you(!)
   Not sure what you mean by dashboard. We are working on ‘My Space’ which would allow users to create views that only they can see (but this would probably conflict with the access permissions model for #3).
   Otherwise, for normal users, a space (and therefore its views) can be totally hidden if that is necessary.