What is the problem or goal the end user is trying to solve or accomplish?
Users would like to more easily define permissions for the guest_token
generation used in Embedded. For example, associate RLS clauses with a dashboardId
(rather than a datasetId
), or even apply logical statement (OR
, etc). It would also be useful to be able to exclude a dataset from an RLS, rather than specify which ones to include. For example using { "dataset": !42, "clause": "state = 'published'" }
would apply this rule to all datasets, except dataset ID 42.
How are they solving it currently?
Currently not possible.
What is the recommended solution by the Customer?
Provide the ability to associate RLS rules with dashboardIds
and also use logical statements in the RLS definition for a guest_token
. Also improve the options to specify which datasets should be impacted by the RLS (such as using exclusion rules).