View privileges i.e. privileges that have a view as privilege object define permissions users have on a specific view. The effective permissions a user has on a specific view can be inherited from all parent views of that view, the system permission All permissions on root views is transformed into all available view permissions on all root views.
Note that only public views can be privilege objects, i.e. you cannot define privileges on private views. Private views inherit privileges from their parent view.
There are only two permissions that are possible to set on a view, list features and list views within view.
Permissions to control modification of features and observations are since 2020 moved to the feature type editor and domain privileges.
Permission |
No |
Description |
Modify view (0) |
0 |
Defines if a user can modify the view settings. |
List features (2) |
2 |
If this permission granted the member features of of the view can be listed. Listing features allows reading the feature's identification data only, it does not implicitly give full read rights to all the features of the view. If this permission is defined in a privilege for a view it is propagated to all subordinate views of that view. |
List views (3) |
3 |
If this permission is granted, user can list the subordinate views of the view and can read the view definition. For a user to be able to list a root view this permission has to be granted on that root view. |
Modify view privileges (4) |
4 |
Defines if a user can modify privileges of the view |
Modify subordinate views (5) |
5 |
If this permission is granted, the user can modify subordinate views |
Table 1: Permissions that can be granted to view privilege objects
