Solved: 1 Dashboard, multiple user dynamic connection - Page 2

P1eter1 · 10-03-2024 05:37 AM

Hello, I know everyone is facing the same problem and no accurate answers are given.

I have 2 service account (1 for fine grain, the other masked ) because i am using policy tags in Big Query.

On looker, i should create 2 connections because each has different service account.

My question is :.

1-Depending on the user attribute, how would i change which connection to use?

2-If not the connection to change., how would I have 1 dashboard reading 1 explore but to point if user attribute['db.'] = true, use connection general else user connection masked or something similar.

Because there must be a way to separate the users without creating multiple explore. dashboard, etc.

Thank you

Kevin_F_McCarth

Hello P1eter1

Core a version of Looker which runs natively on GCP infrastructure. Because you don't see the option Andy mentioned, I'd assume you are on 'Classic' rather than Core. One quick way to double check if you are on core or not: If you are an admin you can check whether Labs admin page is present on the instance (Labs page is not currently provided on Core).

FWIW, as an alternate avenue if you are unable to achieve the dynamic connection settings here you require...
While you cannot have one (technically) dashboard use different models or connections dynamically based on a user, I have seen customers with similar needs use singular lookml_dashboard definitions with different models (which in turn have different connections).

Queries from a lookml dashboard will by default use the model that the dashboard has been included in. So, if you remove all model parameters from dashboard lookml and include the dashboard in both models (which could each include the relevant explores), you get two copies of the lookml_dashboard using their respective models (and thus respective connections -> service accounts). Not a simple solution because you are having to use/maintain lookml dashboards, but with some additional processes in place for publishing dashboards, that approach can work if it's absolutely required.

- Kevin

View solution in original post