Solved on the forum

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.

Documented from current sourcesIntermediateReviewed Aug 16, 2026
THE 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.

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.

Completeness83%
Index decisionIndex now
Evidence basisAccepted forum solution or release plus current official Adalo documentation; no hands-on builder reproduction
WHAT YOU’LL HAVE 🎯

The intended outcome

Joining an event grants the user access to that event’s messages without creating an unnecessary Chat record.

BEFORE YOU START 🧰

Requirements

  • Users, Events, and Chat Messages collections
  • A many-to-many attendee relationship
  • An Event-to-Chat Messages relationship
  • A Join Event action
BUILD IT 🛠️

Step by step

  1. 01

    Model event attendees

    Create a many-to-many relationship so Users can attend many Events and each Event can contain many Users.

  2. 02

    Relate messages to events

    Give every Chat Message one Event relationship; one Event can then contain many Chat Messages.

  3. 03

    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.

  4. 04

    Gate chat access

    Show the chat button only when Current Event’s attendees contain Logged-in User, and filter messages to Current Event.

  5. 05

    Secure the data path

    Review collection permissions and message-creation rules so visibility is not the only access control.

WHY IT WORKS 🧠

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.

COLLECTIONS AND RELATIONSHIPS 🗃️

Data model

CollectionImportant propertiesRelationships
EVIDENCE CONTEXT 🔎

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.
IF IT DOESN’T WORK 🧯

Common failure modes

Joining creates an empty event row

Change the action from Create Event to Update Current Event, then add Logged-in User to the attendee relationship.

Current Event is unavailable on the chat screen

Pass Current Event in the link action and confirm it appears under Available Data.

BEFORE YOU MOVE ON ✅

Testing checklist

0 of 7 checked on this device

BOUNDARIES 🚧

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.

Current evidence screenshots have not yet been added. Treat the guidance as documented or legacy material according to the status shown above.

BUILDER REPORTS 🗣️

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
VERSION NOTES 📝

Sources and status

This page was last reviewed on Aug 16, 2026. Its current status is Documented from current sources.

Verification owner: Automatically organized from an accepted forum answer; monitored for corrections. Next review: Oct 16, 2026.

VERSION HISTORY 🕰️

Changelog

  1. Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.

SPOT SOMETHING FUNNY? 🕵️

Report this answer.

Forum answers post automatically. If a step is wrong, outdated, unclear, or missing an important boundary, send the exact correction and the editor will check the live page.

Report a problem
MONTHLY APP MANAGEMENT · BY REHOST

Rehost becomes the monthly team behind your app. Fixes, releases, integrations, and ongoing changes have an owner.

See monthly management
FixesHandled
ReleasesHandled
Next changesHandled
YOUR PROBLEM IS DIFFERENT? 🤔

Bring us the messy version.

Describe what you expected, what happened instead, and what you already tried.

Ask Adalocado 💬