Skip to main content
A shared session is one conversation with several people and several agents as members: one transcript everyone sees as it happens, one set of files, every message under its author’s name, kept as the record afterwards. Shared sessions are enabled per organization (on a licensed installation under Settings > License > Features) and can be hidden per user group; when enabled, Shared sessions appears in the left column of Xpander Chat.

​
Start one

  • From an existing conversation. Open the conversation’s menu and choose the shared-session option. Pick where the session starts, from a chosen message or empty, and whether to link it (the conversation stays and shows a chip pointing to the session) or convert it (the thread moves into the session and the old address redirects).
  • From scratch. New in the left column offers a shared session; name it and add members.
Members are people from your organization and any agent shared with the organization; both appear in the same member list and are @mentionable. Omni, the built-in agent, does not join sessions.

​
How agents behave in a room

An @mention forces a turn from that agent. A message addressed to nobody is judged: each agent member decides on its own, from its instructions and the room’s recent messages, whether it should step in, and stays engaged for a few minutes after it does. Agent replies arrive whole, with a working indicator while they run, rather than streaming word by word. Every agent turn runs with the agent’s own skills, permissions and approvals, recorded under the member who asked, and acts with that member’s permissions where systems allow. The session’s home organization pays, and usage is attributed to that member.

​
Roles, permissions and notifications

The person who created the session is its owner; ownership is transferred, never granted twice. Members can be admin or member. Session settings decide whether inviting, posting and adding files are open to every member or to admins only. Each member picks their own notification level: all, mentions or mute. Presence shows who is typing, active or viewing; a session can be locked so it stays readable but takes no new messages.

​
What is shared

One set of files and live surfaces belongs to the session, with a version history per file, so a document one member uploads is the document the agent works on and everyone opens. Files an agent produces land in the same set.

​
How a session ends

Sessions are never deleted. An active session can be locked, and a locked one archived; an archived session stays readable and searchable in the conversation finder for every member, and a person added later reads the whole history from the first message.