How do you add event attendees to an event chat in Adalo?
Use the Event record as the conversation, relate attendees and messages to it, and allow chat access only after a user joins the event.
Short answer
Use a many-to-many relationship between Users and Events for attendees, relate each Chat Message to one Event, and add Logged-in User to the Event when the Join button is tapped.
The intended outcome
Joining an event grants the user access to that event’s messages without creating an unnecessary Chat record.
When an event has exactly one chat, avoid duplicating the parent record. Store membership on the Event, relate messages to that Event, and update the existing Event when someone joins.
Requirements
- Users, Events, and Chat Messages collections
- A many-to-many attendee relationship
- An Event-to-Chat Messages relationship
- A Join Event action
Step by step
Step 1: Model event attendees
Create a many-to-many relationship so Users can attend many Events and each Event can contain many Users.
Step 2: Relate messages to events
Give every Chat Message one Event relationship; one Event can then contain many Chat Messages.
Step 3: Update the existing event
On Join Event, update Current Event and add Logged-in User to its attendee relationship. Do not create a new Event row.
Step 4: Gate chat access
Show the chat button only when Current Event’s attendees contain Logged-in User, and filter messages to Current Event.
Step 5: Secure the data path
Review collection permissions and message-creation rules so visibility is not the only access control.
The underlying logic
When every Event has exactly one conversation, the Event record can be the conversation parent.
Attendee membership determines access, and each message’s Event relationship supplies the list filter.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
What still needs checking?
- This is a forum-native answer with no original Adalocado video.
- Current relationship guidance warns that large many-to-many fields have performance costs and recommends join collections as complexity grows.
Common failure modes
Change the action from Create Event to Update Current Event, then add Logged-in User to the attendee relationship.
Pass Current Event in the link action and confirm it appears under Available Data.
Testing checklist
0 of 7 checked on this device
Current limitations
- For large or complex conversations, a separate Conversation or join collection may scale better and carry chat-specific metadata.
- Conditional visibility alone is not sufficient protection for private messages.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts, not endorsements or independently reproduced results.
Add users to event chat when they join
Use the Event as the conversation parent, add Logged-in User as an attendee, and relate messages directly to the Event.
Boundary: A later reply was needed to clarify why a separate Chat collection was unnecessary for one chat per event.
Flawless (accepted answer), clarified by Victor · September 2025
Sources and status
This page was last reviewed on Aug 16, 2026. Its current status is Documented from current sources.
Verification owner: Editorially checked against current Adalo documentation and monitored for corrections. Next review: Oct 16, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Automatically organized and maintained by the Adalocado editorial team under the editorial and verification policy.
Report this answer.
Automated Answers still pass evidence and publication checks, but they can be wrong, outdated, unclear, or missing an important boundary. Send the exact correction and the editor will check the live page.
Did this solve your problem?
One-click check
We’ll handle the tech. You can exhale.
Bugs fixed. Updates shipped. Publishing handled.
$97/mo for your first 3 months.
Cancel anytime. That’s about 90% off the usual cost. 🤯
- Bug fixes and troubleshooting
- App updates and integrations
- Publishing and store releases
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
