> ## Documentation Index > Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Messages > Conversations with colleagues and vendors, and the discussion on every record you are part of, in one list. One list of threads and one thread open beside it — conversations you started, and the discussion on every record you have commented on, mixed together rather than split into two places to check. ## One inbox, two kinds of thread | Kind | What it is | | - | - | | **Conversation** | Something you started — with a colleague, a crew, a role, or a whole site | | **Record discussion** | The comment thread on a work order, asset or other record you are part of | A person who commented on a work order this morning and was messaged about it this afternoon has one place to look for both. Record discussions carry the record's name as a badge so you can tell them apart at a glance, and opening one shows a link back to the record itself rather than a duplicate "who's in here" panel — everything else about it is already there. ## Starting a conversation Tick a colleague, a role, a crew, or a site, and the product works out what you are starting rather than asking you to choose a type first: | You tick | You get | | - | - | | One person | A direct message | | More than one, a role, or a crew | A named group, with a subject | | A site | That site's channel — everybody with access to it | A role reaches everyone who holds it, including somebody who joins later; a crew is who actually works a shift together, which is usually the group you meant when a role would have been dozens of people. ### Bringing in somebody from outside A vendor contact with an email address on file can be invited into a conversation, provided they are not already a user. They get a sign-in link and can see the conversation and whichever sites you tick for them — at least one, because an account with none would otherwise reach every site there is. Once an outsider is in the room, a banner says so and a per-message **internal** tick appears, letting you keep a note from anybody outside the company without starting a second conversation. ## Writing a message * **# points at a record** — a work order, an asset or a purchase request — and it renders as a chip the reader can open, or a flat label if they cannot see that record. * **@ names somebody.** * **Attach** adds a file — a photograph of the fault, a scanned delivery note — with a note about what it is, since a photograph nobody wrote a sentence about is a photograph nobody can search for later. * A quick reaction (👍 ✅ 👀 🙏 ⚠️) is one tap on any message. Your own messages show **Seen by** once somebody has read them — asked only about what you sent, never turned into a readership count on somebody else's message. Edited messages are marked **edited**; a message you may remove carries a **Remove** action. ## Managing a conversation Open **In here** to see who is in a group, add somebody, mute it, archive it, or leave — muting and archiving are per-person, so quieting a busy channel does not change it for anyone else. Leaving is only offered on a group you can leave; a site channel's membership is the site's access list, not something you opt out of one person at a time. ## The tray A messages icon sits in the header beside notifications and the sync tray, with its own count — the number of *conversations* waiting on you, not the number of unread messages, because "three conversations are waiting" is a number somebody can act on and four hundred unread messages in a busy site channel is not. Opening it previews the newest few; **Open all** brings up this screen. What gets emailed, texted or pushed about a comment, separate from the conversation it sits inside.