Managing Write Access for Business Users in Motherduck with Service Account-Owned Databases
I've got a use case that is proving difficult in Motherduck. I have a service account that runs my dbt packages, creating tables across 6 different databases. I have shared these databases with some business users, which works great for read only work. However, some of these users have a need to write (running ad hoc scripts that create tables or insert into tables) which can't be done on their shares, and they can't write to the main databases because they are owned by the service account. The only workaround I can think of is to issue the user a token with access to the underlying databases and then have them connect with something like Datagrip or the cli to execute their procedures. Am I missing something fundamental here, or is this the intended way that this work should be accomplished?
.png)