-
Notifications
You must be signed in to change notification settings - Fork 11.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: User removal from Org and Global users #3953
Comments
Also, some kind of confirmation/warning message should also pop up that "Are you sure to remove this user and his 12 dashboards?" Something similar to this. |
but sounds like the dashboards will be deleted |
What if people in the organization wants to keep dashboards created by someone. I think deleting dashboards should be optional whenever the user who created them is removed from the org or from grafana. There can be a checkbox in the removal confirmation modal to remove the dashboards too. |
I do not understand what you mean, when you remove a user, NO dashboards are deleted. |
I think I was not clear before. Let me try to explain the use cases again:
Here is my proposal for "Removing a user from an org or from Grafana": When we delete a user from an org or Grafana, in the confirmation dialog box (modal), we can give an option to retain the dashboards which this to-be-removed user created. By default we can delete the dashboards he created. Let me try showing an image of this confirmation dialog box. :) |
Should it now say something like "Do you also want to delete 10 dashboards created by Tom" ? And should not be checked by default as that would be prone to accidental dashboard deletion Not sure why this is filed as a bug :) seems like a convenience feature |
Changed it as a Feature Request. :) |
I think the problem of deleting dashboards created by deleted users might be better solved by introducting better filtering options in manage dashboards page (to show dashboards created by deleted users, dashboards not opened in last x months etc) We are trying limit open GitHub issues in order to better track planned work or features we eventually hope to implement rather then enumerate all possible features. I will close this issue since it's been open for very long time without much interest in the feature or anyone showing interest in implementing it. This does not mean that we will never ever implement it or that we will never accept a PR for it. A closed issue can still attract up votes and act as a ticket to track feature demand/interest. |
When we remove the user either from an organization or from Grafana global user list, Grafana should unset the "created_by"/"updated_by" fields in the dashboard table for that removed user.
The text was updated successfully, but these errors were encountered: