Copy views to private view section - Permission settings collision

Feature Ideas
1

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.

2

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.

3

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.

4

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.

5

Hey @kuechleo, we’re going to allow editors to duplicate a collaborative view into a personal view. Would that work for you?

6

Yessssss, that would be amazing :smiley: Please keep me updated for when you roll this feature out :slight_smile:

7

@olgatrykush So, this is not a feature for Version 2.0, or is it? :innocent:

8

No, it’s not part of this release, unfortunately :pensive_face:

9

Ping! - When is it coming? :slight_smile:

10

Hey @kuechleo, I can’t say for sure. We’ve added the request to our backlog (where we have 1000+ issues), and from there we prioritize and pick up the ones with the highest priority. On Wednesday, I’ll try to check whether we can get an estimate for the quarter you can expect it in — though I can’t promise we’ll have that information. :slightly_smiling_face:

11

Hey @kuechleo, a quick update: we can’t provide an estimated timeline for this request, but there’s a feature coming up that may partially cover what you need: Copy configurations from one view to another · Issue #2762 · baserow/baserow · GitHub. It’s a high-priority one for the next year — hope that helps! :slightly_smiling_face:

12

@olgatrykush Any news on this feature? This currently is very high on our “most wanted” feature list!

( especially that editors do get the button “to personal”, but clicking it always causes an error, which frustrates new users a bit)

13

Hey @dev-rd, no updates yet, but I’ll double check with the team.

Our priorities change often, so it’s hard to say when we’ll work on a particular feature. :raising_hands:

14

Hello @dev-rd, I just wanted to let you know personally that we discussed this with the team, and we’ve prioritized the copy view configuration feature. We plan to implement it this quarter.

The dev team will also look into the “To personal” permissions mismatch. :slightly_smiling_face: