Messenger

Messenger is Infra One’s signed-in inbox for conversations with people, groups, Ori, and support. It is not an organization-wide mailbox: access follows participation in a room, with separate resource access for linked fund conversations.

Opening Messenger ensures that a personal Ori conversation exists. On a first visit, this can create the personal Ori room and its memberships before you select a chat, but it creates no message and sends no notification by itself.

Conversation types

Messenger supports direct conversations, group chats, personal AI with Ori, and support requests.

Conversation	How it begins	Who can open it
Direct	Selecting an existing pair reuses its room. A new pair remains a draft until the first message or attachment is sent.	The two participants.
Group	Create group immediately creates the room, records its creator, and adds the selected members.	Current room members.
Personal Ori	Messenger creates or reuses the signed-in user’s personal Ori room.	The signed-in user and Ori.
Support	New support request immediately creates a new group-backed support room with the requester and Ori.	Current room members.
Linked product room	A fund or another product workflow creates the room outside Messenger.	Current participants, or users who satisfy the linked resource’s access policy.
Website chat	The website-chat flow creates the room and its initial memberships. It does not come from Messenger’s New chat menu.	The visitor and explicitly seeded participants. An organization role alone is not enough.

Website-chat membership is read-only in Messenger. Keep embed and visitor setup in the website-chat documentation; do not use the group-leave control that can appear in the shared header for these rooms.

The inbox

• All contains active conversations available to the signed-in user, except direct contacts that this user blocked and rejected direct requests.
• Archived contains rooms that this user archived, except a self-blocked direct conversation while that block remains.
• Blocked contains direct contacts that this user blocked and takes precedence over All and Archived for those conversations.
• Filter narrows the currently loaded room list.
• The pinned AI row stays separate from ordinary chats and reflects the most recently active AI conversation in the current tab.
• Support rooms appear under Support.

Archiving and blocking are user-specific inbox states. Neither one grants or removes access to every room associated with an organization.

When Messenger writes data

Action	Durable effect
Open Messenger for the first time	May create the personal Ori room and two memberships. It does not create a message.
Select a new direct participant	Opens a draft only. No room exists until the first send.
Open an existing room	Updates the current user’s stored last-message-seen timestamp and clears the displayed unread count. A first fund-room open based on linked resource access can also create that user’s room-membership row.
Receive a message in the room currently open	Updates the current user’s stored last-message-seen timestamp and clears the displayed unread count for that room. This is local inbox state, not proof of another participant’s receipt.
Send the first direct message or attachment	Creates the room, memberships, and message. A new person-to-person pair starts pending; a bot-backed pair starts accepted.
Create a group	Creates the room, creator record, and memberships before a message is sent.
Start a support request	Creates a fresh support room with the requester and Ori before a message is sent.
Send a message	Persists the message and updates room activity. Notifications and AI work happen afterward and may complete separately.
Add, remove, or leave	Changes room membership and can transfer group ownership.
Archive, block, react, edit, forward, report, or delete	Writes the state described in Messenger permissions and states.

Durable success and safety

A room in the inbox, a message in its transcript, or a changed participant/state record is durable success. A banner, push notification, AI response, or another participant’s read state is not proof that the underlying write succeeded.

Use only reviewed identities and content authorized for every participant. Messages, files, reports, and support requests can contain sensitive information; never copy customer data or private conversations into examples or documentation captures.

Start using Messenger

Follow Start a direct conversation for the first-send boundary. Continue with Run Messenger workflows for groups, AI, support, attachments, message actions, archive, and block controls.

Related pages

• Start a direct conversation
• Run Messenger workflows
• Messenger permissions and states