Coordinate in team chat
Use organization and server channels, threads, mentions, and references to keep operational discussion next to the servers it concerns.
Chat is a message space for the members of one organization. Use it for handovers, incident discussion, and questions about a server. It is not connected to in-game chat, and players cannot read it.
Before you begin
Open Chat in the organization sidebar. Members need the team-collaboration plan feature for organization workspace operations, which include chat. Owners and admins create and archive channels.
Choose a channel
Channels have one of two scopes:
| Scope | Who can read it | Use it for |
|---|---|---|
| Organization | Everyone in the organization | Announcements and work that spans servers |
| Server | Owners, admins, and members who can access the server | Discussion about one server and its alerts |
A member who has no access to a server does not see its channel. Do not use a server channel as the only place for information that the whole team needs.
Create or archive a channel
As an owner or admin:
- Choose Create channel.
- Enter a name of up to 80 characters and, optionally, a description of up to 300 characters.
- Select the scope. For a server channel, select the server.
- Create the channel and send a first message that states its purpose.
To retire a channel, use Archive channel in its options. An archived channel no longer accepts messages. An alert contact point that targets it stops delivering there, so update alert routing first.
Write a message
A message can contain up to 4,000 characters. You can also add:
- Mentions: up to 20 teammates per message. A mentioned person finds the message under Mentions.
- References: up to 10 servers, incidents, or activity events per message. A reference links the message to that record.
Use Reply in thread to keep a discussion together under one message. Edit or delete your own message from its message actions. Owners and admins can also delete another person's message. An edited message shows an edited label.
Do not paste agent keys, API keys, or passwords into chat. Every member who can read the channel can read the message.
Set your notifications
Open Channel notifications and choose one setting for each channel:
- All messages: notify you about every new message.
- Mentions: notify you only when someone mentions you.
- Muted: do not notify you.
This setting is personal. Browser and operating-system permissions also affect delivery. See personal notifications.
Send while offline
Chat needs a connection. If you are offline, choose Queue message to keep the message on this device. Enderdash sends it when the connection returns and keeps retrying for seven days. Review a queued message if the situation changed while you were offline.
Unsent text stays as a local draft for seven days. See the installed app for draft and share behavior.
Receive alerts in a channel
An owner or admin can add a chat contact point that targets a server channel. Incidents for that server then appear in the channel. Follow alerts and delivery routing.
If chat or a channel is missing
- Chat is unavailable for a member: check the team-collaboration plan feature.
- A server channel is missing: check the member's access to that server and whether the server is frozen.
- A channel disappeared: an owner or admin archived it.
- A queued message was not delivered: check that you are still a member of the organization and can still read the channel.
Next: invite people and grant access.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on