Define dashboard behavior for user 1

Given that progress in the issue this one is postponed on 📌 Add a container parameter that can remove the special behavior of UID#1 Fixed is not going as fast as we would like to, we decided to work on this one to unblock it.

After some thinking, created a MR where the logic has been modified to check for the specific permission instead of checking if the permission belongs to any of the user roles.

The result of this change is hat user 1 will have access to all the published dashboards, while the res of users logic will remain as it was.

I think this is a compromise solution until the arrival of 📌 Add a container parameter that can remove the special behavior of UID#1 Fixed .

Given how close 📌 Add a container parameter that can remove the special behavior of UID#1 Fixed might be to land, this looks like the right call.

Oh, so close that it landed a week ago! Still current behavior remains by default though.

Yep, I believe we will still to use this workaround - or a different one - for now.

I like the MR, is this something we can add a test for?

Good point!

I don't know well how to replicate the user 1 behavior in kernel tests after 📌 Add a container parameter that can remove the special behavior of UID#1 Fixed .

Actually this MR is agnostic and gives the actual responsibility to the site administrator.

If they decide to give superpowers to user 1, they'll access to all the dashboards.

If user 1 is not empowered, it would behave like any other.

Don't think we need to add extra tests to confirm the default behavior.

If you feel safer having them, we could explore how to make it possible.

LGTM!

MR merged. Opened 📌 [PP] Define specific tests for disabled super user access policy Active to implement extra tests for disabled super user access policy once it is added to a stable release.

Automatically closed - issue fixed for 2 weeks with no activity.