Good point 👍

I think it may be possible to add 1) "reset by themselves" easily. 2) and 3) are currently a bit more effort and is probably not realistic. I could maybe add 1) in Piwik 3but not sure where it would be best placed and how it should be named. Any idea?

For # 1 it could be simply under Personal Settings, right under "Exclude your visits using a cookie" ('im using 2.16 so it may be different under 3.x).

For # 2 it would make sense in the "User Management" section since we already have the user ID and the SQL query to perform is known.

For # 3 Administration => Users is where it makes sense.

I presume your concern about how easy it is to add those is related to code quality and make these "clean" and not "hackish" like running the queries by hand... I'm just a simple human being so I don't know what's hidden behind my suggestions usually... ;)

As for a title I think "Reset visualisation" with a short description of the impact : "Clicking this will erase visual preferences of your reports like number of rows showed or the kind of graphs you used to see back to a default Piwik installation. No data will be lost, just the way you used to see it if you changed any visualisation setting."

My concern was it is just more effort to implement #2 and #3 nicely as it involves finding a nice solution, security checks, even more explaining in the UI when it is useful and what it does etc. The user management is already quite bloated and the feature will be rarely needed so it's a bit tricky to solve :)

Maybe we could have a general "reset settings" button under the "exclude cookie" that also resets a user's plugin settings etc? I'm finding it hard to add a "Reset visualization" because it may be a bit confusing although your explanation is really good and useful 👍

We've had around 4-5 customers who ran into the issue with reports not loading due to visualisation settings. Some users had to resort to deleting their user accounts and creating a new one to fix the issue as they didn't have direct SQL access. Having the option to do this in the UI would save a good amount of frustration.