Skip to content
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

Empty permission array for user #14

Open
gheorghelupu17 opened this issue Dec 14, 2022 · 1 comment
Open

Empty permission array for user #14

gheorghelupu17 opened this issue Dec 14, 2022 · 1 comment
Labels

Comments

@gheorghelupu17
Copy link
Contributor

For some deploys of Paul, I have empty tables_permissions why?
Screenshot 2022-12-14 at 12 25 19
Screenshot 2022-12-14 at 12 26 49

@danniel
Copy link
Collaborator

danniel commented Dec 16, 2022

The "tables permissions" list contains permissions per individual "table" (object). That list is empty if there are no tables. For each "table" an user can have "change_table" and/or "view_table" and/or "delete_table". This seems to use a 3rd party permissions package: https://django-guardian.readthedocs.io/en/stable/

The global permission for creating new tables is already enabled for all superuser accounts. This uses Django's default permission system: https://docs.djangoproject.com/en/3.2/topics/auth/default/#permissions-and-authorization
But not sure if we check for this on table creation. (TODO)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants