TL;DR
Use:
- Event updates for official event-level changes
- Eligible event chat for attendee coordination around one event
- DMs for one-to-one follow-up or private details
Standalone private group chat is planned, but it is not currently enabled. Do not create a club merely to imitate a private group unless your crew actually needs club membership, roles, rules, and events.
If everything goes into one thread, you lose clarity fast.
Use event updates for the official record
Event updates belong to the event object.
Examples:
- venue change,
- revised rollout time,
- weather call,
- waypoint changes,
- parking instructions,
- cancellation or major safety note.
These updates should be readable later by anyone looking at the event.
Use eligible event chat for attendee coordination
Event chat is available only when the event and your current participation permit it. It is for conversation tied to that event, not a reusable standalone private group.
Examples:
- convoy timing,
- last-minute regroup notes,
- attendee questions that should stay beside the event.
Official schedule, venue, cancellation, and safety changes still belong in structured event updates so the event remains the source of truth.
Use DMs for private follow-up
DMs are for:
- personal questions,
- contact details,
- edge cases,
- or anything that does not need to stay attached to the broader group.
If the conversation only matters to one or two people, keep it in Direct messages.
Common mistakes
- Putting official schedule changes only in chat
- Treating event chat as the official event record
- Keeping a private logistics discussion in a public community thread
- Claiming standalone private groups are available before the feature is enabled
A simple decision rule
Ask one question:
Should this information remain visible as part of the event record?
- If yes, use an event update.
- If no, but eligible attendees need it now, use the event chat.
- If only one person needs it, use DMs.