Preset Feature Feedback
Problem:
Creating datasets requires a much more advanced set of skills and a deeper understanding of the data than just building charts and dashboards off of approved data sets does.
In Preset you either are a “viewer” and can’t create anything OR you are a “contributor,” which gives users the power to create data sets. In a perfect world, there would be an intermediate role that allows individuals to create charts and dashboards but NOT create datasets, ensuring end users without the right skills to create datasets are *only* working off of approved data sets.
Current workaround:
We are currently asking end users without the right training to not create datasets, and they generally listen, but not being able to enforce that is problematic. Right now we've only onboarded a small portion of our company so it's relatively easy to ensure people are "complying" with this ask → if we chose to onboard a significant number of users over the long term, this gets scary. During our POC with Preset, we had a few users accidentally create data sets just b/c they didn’t know what they were doing and I could see this happening much more frequently
If it’s helpful, this is how we’d envision provisioning access in Preset if we had the ability to limit dataset creation to a set list of users:
All users added to Preset are initially provisioned with “viewer” access. After successfully completing a basic training course on how to use Preset and what data sets have been made available to them, an individual can be bumped up to a “chart/dashboard creator” permissions.
If a user wants to get permission to create data sets, they would need to complete our in-house SQL course, and an additional more advanced training course on how to create data sets in Preset. Once they’ve successfully passed those two courses, they could then be bumped up again to “primary contributor” access which would give them the ability to also create data sets.
