-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This package should document what permission are needed to use these views #13
Comments
Weirdly even as an admin I have difficulty accessing one of these views. I get That could be a separate issue - I can access all the other views. |
Hmmm can you try installing from this fork and checking what happens?
|
No luck, I still can't access that view. Could be something to do with permissions on my side, I can't access a similar view in our own DBT models which uses |
So my issue was that I was creating the users with a non-super user, so even super users could not access the view as it was using the permissions of the original user. We'll resolve that by having a separate DBT run which uses a superuser to create only these views. That probably isn't relevant to the original issue. |
My default analyst role doesn't have the ability to view this relation:
Nor this one:
Important to note, the
dev
schema doesn't even exist at this point (I dropped it earlier today).It seems like these views are only queryable by admins :/
The text was updated successfully, but these errors were encountered: