You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For some of our clients we would like to be able to disable django-check-seo for them, but have it available to ourselves.
Describe the solution you'd like
I would like to add a permission in the default django user admin that we can give to the users/groups that should be able to view the django-check-seo page. I believe the current behaviour should also be supported (only staff users can view the page), therefore I think we can add a setting (e.g. DJANGO_CHECK_SEO_USE_PERMISSIONS) that toggles the behaviour.
Describe alternatives you've considered
N/A
Additional context
In the future we probably also want be able to have access control on a per check basis (so not show all checks to every user), so that could be something that could be considered while implementing this feature.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
For some of our clients we would like to be able to disable
django-check-seo
for them, but have it available to ourselves.Describe the solution you'd like
I would like to add a permission in the default django user admin that we can give to the users/groups that should be able to view the django-check-seo page. I believe the current behaviour should also be supported (only staff users can view the page), therefore I think we can add a setting (e.g.
DJANGO_CHECK_SEO_USE_PERMISSIONS
) that toggles the behaviour.Describe alternatives you've considered
N/A
Additional context
In the future we probably also want be able to have access control on a per check basis (so not show all checks to every user), so that could be something that could be considered while implementing this feature.
The text was updated successfully, but these errors were encountered: