Messaging handles the threads that should not stay in comments.
This hub explains how inbox, direct messages, group threads, and event updates should be used in Drivurs so logistics and conversation stay legible.
- Inbox
- Direct messages
- Group threads
- Event updates
Guides
1 pages
Messaging-specific guidance
This hub stays narrow: when to use DMs, group threads, and event updates instead of forcing everything into community posts.
Split
3 thread types
DMs, groups, event updates
Each thread type exists for a different job and should not collapse into one generic chat pattern.
Coordination
Day-of ready
Supports convoy and meetup coordination
Messaging should absorb the noisy logistics that do not belong in the public event object.
Start here
Open the right surface first
These cards anchor the live app workflow and the most relevant guides for this hub.
Communication model
Use the right thread for the job
Public posts, events, and inbox threads each solve different communication problems. Messaging should take over when the discussion becomes operational or private.
Handoff points
Know when a thread should move out of comments
Questions stay in Community. Structured logistics stay in Events. Everything private or noisy should move into inbox threads before the signal gets buried.
Get early access
Use Messaging when the thread needs privacy, continuity, or live coordination.
This keeps Community readable and lets Events stay focused on the event object instead of comment chaos.