Hi Team, I have a question regarding making our metrics "read-only". I don't see this as a possibility in the documentation. We create metrics/visualizations for our customers, we embed these in our app as well as the "analyzer", we want our customers to be able to use our metrics and see the visualizations we make as well as give them the ability to make their own, but we don't want them to be able edit the metrics or visualizations we make. Any suggestions?

I'm afraid this isn't possible to control at the metric level. You can manage user permission to allow them access to edit/create metrics, or give the user permissions to only view the data and not edit anything. Since you have stated that you would like to have them create their own, but not edit built metrics, we can submit this as product feedback on your behalf. Would you please state how critical this feature would be for you?

Hi Ramtin, actually, this exact effect where all the core objects are locked and not editable can be achieved using the workspace hierarchy. If you build your analytics - data model, metrics, visualizations, dashboards in your parent workspace and then set up child workspaces which inherit all this (and are otherwise empty), the end users of the child workspaces will have read/only access to all these objects within their workspace but will not be able to remove or modify them. And if they have proper permissions, they will still be able to create their own metrics, visualizations and dashboards based on these core objects within their workspace.

Hi Michal and Joseph, thank you for your answers. @Michal Hauzirek will creating the child workspace use up our workspace limit? Or is a child workspace not considered a separate entity?

I believe the child workspace does count to the workspace limit as well as the parent workspace. Typical setup for a multitenant solution with many customers using the same core model and dashboarda but diffetent data is to have one parent workspace and many child workspaces - one for each client organization.

@Joseph Heun This is a critical feature for us as we need to protect assets created by us for our customers while still giving them the ability to create their own, without fear of ruining objects that are necessary for their visualizations. Unfortunately the model of creating child workspaces does not work for our architecture

🎉 New note created.