Mark dashboard/reports/views as global so they don't get deleted with users or allow bulk migration

55 votes

As it is you are forced to clone a view and delete the old one for a user to take ownership.
An alternative is to copy user_*.mk files in cli under var/check_mk/web/user but those files don't have unique names so it's not a great option to bulk migrate to a service account (which comes in handy when migrating authentication sources)

Under consideration Dashboards & Views Suggested by: Martin (18 Jul, '22) • Upvoted: 17 Apr • Comments: 7

Comments: 7

19 Jul, '22
Daniel Roettgermann
More or less the same
https://features.checkmk.com/suggestions/301814/impersonate-as-another-user-to-check-views-and-dashboards

Could be merged
19 Jul, '22
Lars Sörensen
Make the ownership of dashboards/reports/views editable for administrators so they can assign a different user or service account.

And to check how dashboards/reports/views look like for other users:
https://features.checkmk.com/suggestions/301814/impersonate-as-another-user-to-check-views-and-dashboards
19 Jul, '22
Thomas Lippert Admin
I think it is a related but still different use case. This use case is about detaching views/dashboards/reports from a user. The "Impersonate" use case is about a temporary ownership to work on behalf of a different customer.
Implementing this feature might allow getting mostly the same as the "Impersonate" feature request. But the other way around would not solve this use case
19 Jul, '22
Daniel Roettgermann
build in or "dashboard/view user is the same.
loosing the dashboard/view/report because of a user leaving the company and the system get cleaned is the main problem, which would be solved fully with
https://features.checkmk.com/suggestions/301814/impersonate-as-another-user-to-check-views-and-dashboards

as lars wrote, if you are able to change the owner ship, on the filesystem, it would move from one file to another as well
Bulk edit for user ownership could also be "easy" implemented. Select all views/dashboards/reports and change to user XYZ
19 Jan, '23
gt_whaid
One would think that in an _enterprise_ environment on- and offboardings are common. I'd also assume that CheckMK LDAP and/or Active Directory integration is a frequently used feature.

Thus, dashboards might be created for _company_ use rather than personal. Having those dashboards disappear, which might be in use by whole teams, when individuals leave, is a no-go imho. At least not for anything which claims to support an enterprise.

At first I actually thought this is a joke when I was told about this. Unfortunately not.
19 Oct, '23
Volker L.
As a workaround, we currently use a dedicated account for creating non-personal views. We test the functionality with a test account to which the respective rights are explicitly assigned. Of course, this is a bit cumbersome.
06 Mar
Thierry T.
To add to the list: custom graphs is another case where this would be useful.