Hey there,
By any strange mystery, probably an upgrade (0.36 to 0.37 and 0.37.1, successfully), one of my users in my Rocket.Chat install can't send DM anymore to other users…
Here is what it looks like, basically the message box is… empty!
I tried to rename the username to find a solution/fix, but no result.
Is there any solution to "reset" the user without deleting existing messages? Or create a new user and change the author to this new one?
Any help appreciated!
Rocket.Chat version: 0.37.1

After changing the username to the first one (let's say "superuser" - it was "superuser-" just for testing), I have this home… no sidebar, nothing. What is the point?!

Looks like a "role" issue… it was set for an unknown reason to "null". Setting back to "user" sounds to do the trick. But why did I got a "null" role at some point?
I have the exact same issue on another site.
Channel names doesn't show up, channel links that other users send to me says that the channel doesn't exist. Nothing works except for the status and settings.

You can see that I have 2 private message (in the page title and the favicon).
EDIT: I can get correct results using the API!
@SafaAlfulaij what did you do with the API to work then?
what did you do with the API to work then?
Just used it, check this: https://rocket.chat/docs/developer-guides/rest-api/
I mean the API url results give the correct results (My account is working). The problem is with the UI only.
@Flayks Yes this was a problem with the roles system but it was probably solved in pr #4073 , and it should not happen again. Thanks for the report, and if the bug still exists now, please report to us
In 0.37.0 you can achieve same result (loss of permission) by changing another user's password.
Can fix this by adding user to users group in permission page.
I'm having this issue too although I'm not 100% sure what is causing it. I thought it may have to do with my slack-bridge but now curious about the password change bit. Is there an easy way to bulk add all users back to the users group (if thats not a bad idea)?
I found that it was only about 6 or 7 users for me that were affected so I updated them manually in the DB. Hoping after the last upgrade I did that I won't see this issue any longer.
This have been fixed on later versions.
Most helpful comment
In 0.37.0 you can achieve same result (loss of permission) by changing another user's password.
Can fix this by adding user to users group in permission page.