Marin Š.

Thanks! once you have the tenant rw token - can this be somehow triggered from my app to open new tenant db and assign rw token for flight, dives, and other. and how to flights then receive and store that specific token for that db? so that daily they update lets say 10 tenant dbs from single central flight?

and how provisioning works - can central flights create tenant db's? I also have app where tenants are initialy created - they need to flow somehow to motherduck for provisoning/scoping. App in the end has embedded dive, and should choose db that belongs to that users tenant

do they need to be shared to central db or? - did not get this - central flight has rw token for each tenant db, but do tenant db need to be shared/attached to central service account also?

This will have read access to your central DB because it's tied to your "central" service account - only read or rw?

thanks! token that came with the flight to read from the central db - this does not need to be in secrets - it is service account flight?

so in that case central accout has rw token for each tenant db - do they need to be shared to central db or? do you suggest build like this or something better?

Yes - i understood that is best practice - or you have some other solution? But should each service account have read access to central DB if they are scoped only to their part of data in their DB?

Question regarding Flights - we are building multitenant setup. service account owns central DB, which would then need to build tenant DBs - each under its service account. And we need to daily update those by central flights. they are updated using data from central db but also with using private data under each db which is joined to central data. Is this right setup? How it works with flights? Thanks

Flights are loading now!