Standard or custom reporting?

Vizzly offers standard and custom reporting. Standard reporting means your users will get a read-only view of the dashboard you build for them. They can make simple changes to explore the data such as using pre-configured filters and parameters on each chart.

Alternatively, by utilizing Vizzly's custom reporting you can allow your users to make changes to their very own dashboard. You can control the degree of customization you allow your users to make by using our extensive set of feature toggles. For example, you might give them all the tools that are available to build the dashboard, or you might restrict them to picking from a library of charts that you have built for them.

Standard reporting (read-only)

Show your users a read-only view of the parent dashboard that you have built. You can create one or more parent dashboards that your users can toggle between to show different data "stories".

Implementation

1. In your identity config, you will need to set the scope to read.
2. Set the parentDashboardId dashboard property.

Custom reporting (read & write)

Also known as "self-serve" analytics, custom reporting allows your users to modify their copy (a child dashboard) of the parent dashboard you have built.

You can still provide updates to child dashboards by populating the parent dashboard's library with more charts. Any chart in the parent dashboard's library will show as "verified" in your users libraries!

Implementation

1. In your identity config, you will need to set the scope to read_write.
2. Set the user reference in the same identity config to a unique identifier for each of your users, or a group of users.
3. Set the parentDashboardId dashboard property if you will have multiple self-serve dashboards throughout your application.

Read and write access within a user group

In SaaS products, it is very common to have groups of users such as 'organisations' or 'teams'. Within each 'organisation' or 'team' on your platform you might want to control which users have read access, and which users have write access.

Implementation

1. In your identity config, you will need to set the scope to read_write for those in the group who should have write access. For users in the group with read access, you will need to set the scope to read.
2. Set the user reference in the same identity config to be a unique reference of the group.
3. Set the parentDashboardId dashboard property if you will have multiple instances of dashboards throughout your application.

Sharing read-only dashboards between users

To support a dashboard sharing feature, you can setup the identity config exactly how you would for the user's dashboard that you want to share, but then set the scope to read. Then, you can set the parentDashboardId and dashboardId properties on the dashboard, to control the exact dashboard which is shared.