Closed bfuzzy1 closed 2 years ago
There's currently no way to restrict this. On the AuthN and AuthZ roadmap we're working through authentication improvements & SSO support right now which will be followed by local 2fa support and then more granular access control which will cover scenarios like this.
@thebleucheese got it. Do you guys have an ETA for that release?
@thebleucheese got it. Do you guys have an ETA for that release?
Not currently, the SSO & Authentication improvements are next and our focus is currently on testing and delivery for that. Everything mentioned that follows hasn't had enough analysis to estimate a release date.
Ok, thank you.
This should be addressed in 8.2.0. We will provide more documentation soon, but there are some DB Policies available.
Is there a straightforward way to prevent the "user" role from being able to manipulate the databases in the web UI? Ideally, users within the "user" role would not need to make databases changes like that in my case.
Any solutions would be appreciated.