Messages

Request a connection

Find peers by name and use the request state shown by the directory. Incoming and sent requests stay separate so you can take the correct action.

• A colleague who has turned off profile visibility in their own Privacy Controls will not appear in Find Peers or search, and a connection request to them will not go through. This is their choice, not a directory failure.

1. Sign in and open Messages, then choose Find Peers.
2. Search the directory or filter it by the available connection state.
3. Choose Connect for a peer, or use Peer Requests to Approve, Deny, or Cancel the request shown there.
4. Wait until the connection is accepted before starting a one-to-one conversation.

Use an accepted conversation

Select an accepted peer to send a message. The conversation shows unread state and read receipts; actions for your own message include edit, delete, and the available reactions.

• If the directory or messages cannot load, use the displayed retry action and do not infer that there are no peers or messages.
• If there are no accepted peers, use Find Peers to begin a connection request.

1. Open the accepted peer from your conversation list.
2. Write and send a message, then check the conversation for the sent state.
3. Use the message actions shown when you need to edit, delete, or react to your own message.

Message history and deletion

One-to-one and Team Chat messages remain visible in conversation history for 60 days. Older messages disappear from that history even if the conversation is still listed; this is expected expiry, not a loading failure.

Messages become eligible for permanent deletion after 90 days. Deletion runs on a schedule, so it may happen later than that point. An organization legal hold pauses automatic deletion, but does not extend the 60-day history visible to participants.