[feature] multiple levels of access control?

[94rain]

Version and OS N/A

Is your feature request related to a problem? Please describe. Currently, we are only able to choose to set a password to restrict access to the dashboard. A visitor will either have full read and edit access to the dashboard (including changing sitewide configurations) if they know the password or no password is set, or have completely no access.

Describe the solution you'd like

For a simple version, we may have roles such as

• owner: with full access to all features, including changing sitewide configurations
• collaborator: have view access and also able to recheck and change some of the entries that are allowed to be edited, but not the website configurations
• view: only have view access

Describe the use-case and give concrete real-world examples When we want to share the monitoring results on the website with some people, but don't want them to modify the rules or accidentally delete an entry, the view role would be quite useful. And sometimes we don't want to let the collaborator change sitewide configurations and we want to protect some entries from editing.

Additional context I am quite open-minded. Just want to start the discussion. Anything is better than the current all-or-nothing access control.

[dgtlmoon]

https://pythonhosted.org/Flask-Principal/

[94rain]

Cool! Thanks for the info.

[jgupta]

@dgtlmoon I need this functionality and can try to develop this. Can you please give short brief on how should I approach this?

[dgtlmoon]

@jgupta no sorry, i will not, i dont have time for it, and i dont have time for looking at PRs related to it, so answer is , no unfortunately.

[jgupta]

@jgupta no sorry, i will not, i dont have time for it, and i dont have time for looking at PRs related to it, so answer is , no unfortunately.

@dgtlmoon I understand. This saved my time. I don't want to work on something that won't be merged.