> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Messaging
> Use Messaging for internal team conversations, direct messages, channel updates, and record-linked discussion without leaving Arcus.
## What Messaging Is For
* **Direct Messages**: private conversations between two Arcus users in the same entity.
* **Channels**: shared team conversations for operations, projects, departments, or exceptions.
* **Resource Chats**: conversations tied to a specific order, account, product, invoice, purchase order, or return.
* **Unread counts**: badges help you spot conversations with new activity.
**Messaging is internal**
Messages are for your Arcus team. Customer-facing emails and document resends live in Communications,
not in Messaging.
## Find a Conversation
1. Go to **Messaging**.
2. Use the sidebar search to filter by teammate, channel name, or resource label.
3. Expand or collapse **Direct Messages**, **Channels**, and **Resource Chats** as needed.
4. Click a conversation to open the message history.
**Use resource chats for work tied to a record**
If the discussion is about one order, invoice, account, product, purchase order, or return,
use the resource chat so the context stays attached to that record.
## Start a New Conversation
1. Click the plus button in the Messaging sidebar.
2. Choose **Group Channel** for a shared channel, or **Direct Message** for a one-to-one conversation.
3. For a group channel, enter a clear channel name and optional description.
4. For a direct message, search for the user and select them.
5. Click **Create**. Arcus opens the new conversation after it is created.
## Send Messages
1. Open the conversation.
2. Type your message in the composer.
3. Use **@** to mention a teammate.
4. Use **/** to link an Arcus object such as an order, account, product, invoice, purchase order, or return.
5. Use the formatting buttons for bold, italic, code, or emoji when helpful.
6. Press **Enter** or click the send button to post. Use **Shift+Enter** for a new line.
**Do not put secrets in chat**
Do not post passwords, security keys, recovery codes, card numbers, bank details, API keys,
private customer documents, or other sensitive secrets in Messaging.
## Safe Internal Communication Rules
* **Use resource chats for record-specific work**: keep order, invoice, account, product, purchase, and return discussions attached to the right record.
* **Keep customer-facing decisions in the workflow**: use documents, emails, invoices, returns, or order actions for customer commitments.
* **Do not use chat as an approval substitute**: approvals, credits, refunds, cancellations, and voids should use their workflow controls.
* **Pin decisions**: pin important internal decisions so teammates can find them later.
* **Link records instead of pasting private data**: object links are safer and easier to audit than copied sensitive values.
## Link Records in a Message
1. Type **/** in the composer.
2. Choose the object type you want to link.
3. Search for the record.
4. Select the result. Arcus inserts a linked chip into the message.
5. Send the message.
6. Click the chip later to open the record preview drawer when available.
## Use Threads, Pins, and Search
* **Reply in thread**: use a thread when a reply should stay attached to one message instead of interrupting the main channel.
* **Pin**: pin messages that contain decisions, references, or next steps the team needs to find again.
* **Search messages**: use channel search when you remember a word, order number, customer name, or topic.
* **Reactions**: add a quick reaction when acknowledgement is enough.
## Manage Members
1. Open the channel.
2. Click the member button in the channel header.
3. Search users to add people who should be in the conversation.
4. Remove members who no longer need access.
5. Leave owners and admins in place unless your team intentionally changes channel responsibility.
## What Happens Behind the Scenes
* Messages are scoped to the current entity, so teams in other entities do not see them.
* Direct messages, group channels, and resource chats are separate channel types.
* Unread counts update when messages arrive and are cleared when you open the channel.
* Mentions and object links are stored as structured message content so Arcus can render them as chips.
* Deleted messages remain visible as deleted placeholders so the conversation history stays understandable.
## Common Blocks
* **No conversations yet**: start a new direct message or group channel.
* **User not found**: confirm the person has an active Arcus user account for the entity.
* **Create is disabled**: enter a group channel name or select a direct message user.
* **Object search has no results**: type at least one searchable term and confirm the object type.
* **Message did not send**: retry after checking your connection and the current channel.
* **All users are already members**: there is nobody else available to add to that channel.
## Related Articles
Use the email log, preview/resend tools, and account communication preferences.
Create customer and vendor accounts with terms, addresses, and preferences.
Build a sales order, add customers, set addresses, and add products.
Find, create, post, send, pay, correct, and void customer invoices.