I was really hoping to address this in the upcoming v1.0.0 release, but eventually didn't want to delay it as it was in the oven for too long anyway. It will probably be addressed in the release after.
Beside the ability to delete a user have you experienced other rough edges in the recent releases? We strive to improve the stability and reduce the rough edges with every release, so really want to hear about your experience.
We noticed a couple of UI irregularities (for example when editing charts the contents or axis labels would disappear). Unfortunately I don't have anything more specific for you right now. I did notice when deleting users it seems that they (and their dependent db objects) actually deleted from the database (rather than flagged as deleted) - for traceability it would be great if they weren't removed altogether.
Though to balance things, let me tell you what we loved about Redash. The user/group/source model is really nice - I appreciated being able to give only our admin group users access to a data source configured with our database master user credentials. The Google OAUTH functionality (and really clear documentation around this) and pre-rolled AMI were a huge plus, allowing me to get our team up and running really quickly. The same goes for the Lets Encrypt instructions (we all use certbot regularly but no-one had to dig through Redash's config files blind - the docs were spot on). The ability to fork queries - superb. Data export was also fantastic.
I was really hoping to address this in the upcoming v1.0.0 release, but eventually didn't want to delay it as it was in the oven for too long anyway. It will probably be addressed in the release after.
Beside the ability to delete a user have you experienced other rough edges in the recent releases? We strive to improve the stability and reduce the rough edges with every release, so really want to hear about your experience.