Hey All, Has there been a change to gooddata work...
# gooddata-cloud
s
Hey All, Has there been a change to gooddata workspace permissions recently? I see now there are • View • View & Save Views • View & Export • View & Export & Save Views Etc.
@Dave Hood fyi
100% feel like something changed here because we setup our groups for export, but in the UI they now show as "view" only. Plus don't seem to include the saved views by default. Did this change recently? Or did we miss an update that this wasn't explained in more detail? Just a note we're trying to release this feature to our production and we're trying to get our heads around what we need to address this.
m
Hi Steve, we recently introduced two new permissions: CREATE_AUTOMATION and CREATE_FILTER_VIEW. These were announced in our release notes here: https://support.gooddata.com/hc/en-us/articles/33800637387283-GoodData-Cloud-September-26-2024 https://support.gooddata.com/hc/en-us/articles/33993729575699-GoodData-Cloud-October-3-2024
s
So the notice on Sept 26th, says its a new permission, What about the export permission?
If you have export permission, does that also include the save view permission by default? Does not look to be included.
m
It looks like the export permission was simply spun off from the view permission, but I can double check internally this for you. Note that only the MANAGE permission Cover the
VIEW
,
CREATE_FILTER_VIEW
,
ANALYZE
and
EXPORT
permissions.
s
there is a natural hierarchy, View < Export < Analyze, etc. Is there a reason for the varying levels of what is included or not? For example saving filter views is about the same level of "access" as view, but has a protected permission set. Like being able to export a dashboard is more restrictive than saving a view. Having this permission set like this makes it hard to roll something like this out to our customers where we have hundreds of groups with the export permission. Technically we would have to go to all groups and add the new permission set.
m
The different permission levels allow for better control over what users can or cannot do in the workspace. For example, while they should not be able to export an insight, they should be able to create and save a view. If you are interested in allowing users with view-only access to export insights and save views, I recommend selecting the corresponding permission, as highlighted below. Would this cover your use case? As for the technical reason why saved views must be offered separately, I'm not sure at the moment, but I'll be happy to ask around. Could you please elaborate on how this is interfering with your release?
s
In a nutshell • each customer has a set of groups for permissions for their workspace • each group has a specific set of permissions at the export level ◦ ie they can view and export • we have almost 2k+ workspaces => 9 groups per workspace ◦ 18k groups to adjust permissions to allow them to save views. Probably nothing we could have done differently other than it seems the hierarchy of permissions seems semi-arbitrary.