A particularly useful feature would be a standard filter to define for a source that is not only immediately applied but enforced with all queries that are made against a source.
That way you could create multiple sources from the same connection where there's a single table with a tenant_id column and then create sources for specific tenants and restrict their access to the source that is meant for them.
I'm thinking about an extra field in the "Connection" step of the source creation wizard where you can e.g. provide something like
And then this gets automatically applied as WHERE tenant_id = 10 AND (...) to each query. Then, to avoid that users can adjust the query so it matches all tenant_id's again, the column can be deactivated in the second step of the wizard.
A particularly useful feature would be a standard filter to define for a source that is not only immediately applied but enforced with all queries that are made against a source.
That way you could create multiple sources from the same connection where there's a single table with a
tenant_idcolumn and then create sources for specific tenants and restrict their access to the source that is meant for them.I'm thinking about an extra field in the "Connection" step of the source creation wizard where you can e.g. provide something like
And then this gets automatically applied as
WHERE tenant_id = 10 AND (...)to each query. Then, to avoid that users can adjust the query so it matches all tenant_id's again, the column can be deactivated in the second step of the wizard.