Associate (filtered) datasets with Integration

2:00 min
Medium

As dashboards are powered by datasets, it's important to also associate the underlying datasets with the Integration. That way, SSO users that have access to a specific integration also have (scoped) access to the datasets used. All datasets used in the dashboards selected in the previous step will be selected by default to avoid "No access" errors when integrating.
In case of a multi-tenant dataset (i.e. containing rows from multiple clients) do not forget to apply the relevant filters on it (more on this below)!

Keep in mind that in order to associate a dataset with an Integration, you should be owner of the dataset as well as the Integration.

When associating datasets with an Integration you have to specify the access rights and optionally add filters.

  • The access right specifies what the user can do with the dataset:

    • 'Can view' - gives an end user the right to query the dataset, but only queries that are used in charts of dashboards that are accessible to the end user.
    • 'Can use' - next to having chart query access, the end user is able to query the dataset using e.g. our Alerting feature, from within newly created dashboards, etc. They are allowed to create their own queries on the dataset.
    • 'Can edit' - next to being able to view and use a dataset, the end user can edit this dataset, i.e. add derived columns, define hierarchies, ...

  • Important! Don't forget to apply (parameterized) filters in case your multi-tenant data setup requires row-level filtering to be applied! Parameterizable filters can be used to dynamically apply these filters by overriding the parameter(s) when requesting a SSO token for your end-user. Instead of using parameterizable filters, you could also specify static filters when associating a dataset with an Integration.

Now that we've got our dashboards and datasets associated with the Integration the initial Integration setup is done and we can move to the next article, which covers how you should implement the SSO authorization request in your backend to grant access to a certain Integration!

Datasetsssoparameters

Need more information?

Do you still have questions? Let us know how we can help.
Send us feedback!

Related Articles

Adding dashboards to a Next.js application
Applying external filter components to an embedded Luzmo dashboard
1:30
Custom dashboard versioning
2:00
Custom events
3:00
Drilling through to another dashboard in your application
6:40
Dynamically initializing a Date filter in the Authorization request
Dynamically initializing a Slider filter in the Authorization request
Dynamically Initializing Dropdown or a Slicer Filter in Embed Tokens
Embed dashboards and/or the dashboard editor in your frontend
3:00
Embedding a Single Chart In Your Application
0:50
How to query a dataset via our API
10:00
Introducing embedded dashboards and the Embedded Dashboard Editor
2:30
Loading a dashboard in the same filter state as a user left it
Managing the access granularity of your dashboards and datasets
10:00
Migrate from Temporary Token to Embed Token
1:40
Multi-tenancy: an overview of the possibilities
2:00
Multi-tenancy by adding static filters
3:30
Multi-tenancy by overriding data source properties
3:30
Multi-tenancy by using parameter filters
2:30
Multi-tenancy via a plugin with internal logic by adding metadata to your embed authorization request
4:00
Parameter types for parameterizable filters
Request an embed token in your backend
3:30
Retrieving a List of All Dashboards Using a Specific Dataset and Vice Versa with the API
2:00
Supporting different development environments
4:00
Using additional data in interactivity features
What is possible with dashboards integrated with embed tokens?
3:30