Messages is the internal organisation conversation layer. Its underlying module and permission keys remain
team; the product name is Messages. Conversations may link operational work, but messages do not replace
the source task, shift, contract or maintenance record.
Screens and conversation workflow
Messages, /messages?section=updates, offers channel/direct-conversation navigation, unread state, search
and the current conversation. Within a conversation, Messages, Pinned and Files change the
loaded-history view. Earlier history loads in pages. Search starts at two characters and returns only currently
accessible conversations; a result opens its source message.
Create a channel with a title, audience and retention period. Public channels are available to people with Messages access; private channels need explicit Person membership; a group channel can derive membership from a People group. Direct conversations contain two to eight People and do not become manager-readable because a manager administers ordinary channels.
Compose a message or thread reply, optionally mention a permitted person and attach files. The draft accepts up to ten JPEG, PNG, WebP, PDF or plain-text files of up to 10 MB each, previews them before Send, allows removal and supports files without text. Selecting a file does not publish it. Reactions, pinning and thread replies keep discussion attached to the original message. Create linked My Work item captures title, assignee and optional due time while retaining the conversation reference.
Channels provides membership and archive controls. Files collects files from permitted loaded content. Moderation removes content with a reason; removal also affects search/delivery while retaining bounded audit evidence. Channel retention is explicit, with a form range of 7–3,650 days.
Knowledge and learning
Knowledge lists published knowledge available to the current audience. My training lists assigned learning and the state of each assignment. Manage learning supports draft knowledge, exact-version publication and assigning that version. Supported knowledge types include handbooks, how-tos, training and quizzes. These are operational learning records inside Messages, separate from Soupy’s product help.
A manager creates title, summary, body and type. The current web form creates an organisation-wide draft, requires acknowledgement and provides a first quiz question with two choices and a 100% pass mark. Editing an existing document preserves its existing audience and validity metadata; the backend supports richer question and policy records than this form exposes. Publication is explicit. Assign a published version to up to 25 active staff with an optional due date; training/quiz assignments are marked required for eligibility. Staff without a linked login retain their assignment but receive no My Work item until linked.
Staff read the exact assigned version, acknowledge where required and answer every quiz question before submitting. Attempts retain score and pass/fail evidence; a successful completion may expire according to stored validity policy. Rotas consumes current training eligibility without rewriting learning history.
Training detail and eligibility use current source permissions. An assigned person can read their exact assigned version after a newer version is published; other readers need current training-management authority over its audience. Changing or publishing a document requires authority over both the existing and proposed audiences. Web and native detail clear when their current access receipt expires or access is lost. An incomplete eligibility scan is unavailable rather than treated as a complete answer.
Permissions, drafts and settings
team.view grants permitted reading and participation; team.manage governs ordinary channel creation,
membership and moderation. team.training.manage controls learning management. team.settings.view and
team.settings.manage control the dedicated settings route. Channel membership does not grant another module's
capability, and employment alone does not grant access to Messages.
Uploads belong to the sender, current entitlement, channel/thread and draft. Staged uploads expire after 24 hours; Send consumes them with the message. An uncertain Send freezes the exact submitted payload for resolution. Web drafts are separated by channel/thread while the workspace is mounted; native drafts retain encrypted local evidence across restart. Reconnection does not upload or send a draft automatically.
The settings route currently provides General, Channels, Posting and Automations section shells; channel retention/membership are edited in the operational workspace. Soupy-authored automated posts identify their source and linked record. The backend declares a source-labelled automated-message destination; the current general Automation builder does not expose an event-to-channel posting editor. Messages does not itself authorise the source action.