I used the built in conversation feature in adalo and it added me the databases too but when I test it as soon as I click a user to start chat with it gives me unauthorized error under the screen. This happens on 95% of my many-many relationships too… can anyone please help me.
The users collection shows me the unauthorized error everytime I try to create a new chat with a user… I used the built in chat feature by adalo I didn’t add or remove anything I just added the chat feature from the features template and I set a button on my home screen to take to the new chat modal and everytime I click a user it give me the error. I didn’t even touch anything but it always gives me unauthorized error
Hi @Ananiya,
What’s the permissions configured for the users collection as it looks like the full name isn’t showing?
Thank you and have a great day!
The names are empty because I didn’t add names for my test users… the users permission is adalos default I didn’t change anything…
Hi @Ananiya,
Any screenshots? You imported users through a csv file or manually added these users?
Thank you and have a great day!
I think the reason is that there is no “logged-in user” in this screen. Examining browser console (and network queries) can help.
But identifying the cause of the issue requires proper explanation of the issue (screen recording is better).
E.g. no names in the list can mean that the list is connected to a wrong collection; but then it turns out there is no names just because there are no names in the DB - so how this could be guessed remotely by anyone?
I’ve tested @Ananiya’s app and it looks like there’s an issue with the users collection. I properly logged in which can see my information in the app and users names got showed up but the message keeps popping up. It looks like something isn’t working properly with Google signing users (signup through Google signing component) and no record in the users collection can be deleted from the collection view which isn’t normal. Support team will reply to your ticket with a solution in the next couple of days ![]()
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.


