Hello,
I’ve recently played with the permissions settings only to find out one problem:
Editors can not duplicate public views into their private view section.
That’s really bad for us, since one Admin might change a view and all the users, who are building their own private views around it, have to be able to copy it to their own private view section.
However, I want them only to have editor permissions, not builder permissions.
Thus my suggestion:
(I think it should be easy to implement this feature):
Every editor should have the permission rights to copy public views into their private view section.
Also: I’ve just stumbled across a second issue regarding permissions:
It seems that as a commentator I can view data, but not export it…
Why do I have to have editor permissions in order to export the data?
Export rights shouldn’t be on the same level as editor rights.
Thus my suggestion:
Enable export feature for users with comment/view rights.
Hey @kuechleo, I know my colleague already addressed this in direct support, but I’ll duplicate it here for future readers:
A potential workaround is to enable users to export a public view. This option can be activated when sharing a view, allowing users to download the content in CSV, JSON, XML, or Excel format. Once downloaded, they can import the file into their private view.
1 Like
Yes, but this addresses just my second issue, where I want to export data.
However, sensible data should not be openly accessible. There’s the option to protect it with a password, but SSO is not supported. Thus, this option is also sub-optimal for our setup.
The first issue stays: I want to copy updated public views into my private view section (including filters and decorations), even though I only have editor permissions.