Communication holds typed exchanges such as messages, announcements, feedback, recognition and approvals, connected to their business context.
Every exchange here is a typed, connected record — not a message floating in an app. This manual covers the envelope (the one inbox), the fifteen exchange types, the classification each exchange carries, and the wiring to the work it discusses.
What you record
The envelope — one inbox
| Field group | What it holds |
|---|---|
| Participants | From (actor + type), to (actor + type), the recipients list |
| Content | Subject, body, the context module and entity it is about |
| Type | The communication type — message, announcement, feedback, recognition, approval, notification, meeting note, and the rest of the fifteen |
| Classification | The mode (how it traveled), the intent type, the priority, the status |
| Lifecycle | The read-at, the expiry, the active state |
| Mentions | The people named in the exchange — typed, not parsed from text |
The context fields are the quiet power: every exchange can name what it is about — the module and the entity. The thread about the delayed shipment is connected to the shipment's work entry; the recognition is connected to the person and the effort it recognises. Conversation stops being noise and becomes traceable.
The fifteen exchange types
Each type is its own governed shape: an approval carries its decision fields; a recognition carries what it recognises; a meeting note carries the meeting it belongs to. The types are data — the platform knows what a recognition is and what an announcement is, and treats them differently.
The intent and the mentions
Beyond the type, each exchange carries an intent (question, directive, report, decision...) and the mentions — the people the exchange names, as typed connections rather than @-strings. Search for "everything that mentioned Ayşe about the Q3 launch" and the answer is a query.
What you can do
- List, search, filter — by type, intent, priority, status, context, participants; bulk actions
- Create, update, view — the standard patterns; the validation and permissions configured for the operation
- Read-state tracking — who read what, when; the expiry for time-boxed exchanges
- Relate — the wiring below
What it connects to
| Target | Examples of the connection |
|---|---|
| Works | The work the thread discusses or decides |
| Calendar events | The meeting the note belongs to |
| Employees | The sender, the recipients, the mentions |
| Content | The knowledge entries the exchange references |
| Projects | The project the conversation serves |
Where it feeds
Held conversation is the voice of the evidence: the recognition flow the culture readings draw on, the decision trail the process readings follow, the collaboration context that People & Culture Orchestration can examine — all of it begins as typed exchanges here. The communication hub story is the platform page; this manual is the working surface.
The pattern note: same four-part structure — record, do, connect, feed. The communication manual is where the context-wiring pattern shows: the exchange that names its subject becomes evidence with provenance, while the exchange that floats stays noise.
Implementers configure your communication types at adoption — the ones your organisation actually runs; consultants help define the intent taxonomy that matches how your people actually talk.
No record is an island
Every exchange relates to the work it discusses, the meeting it followed, the people it named, the project it serves. The inbox is not a stream here — it is the organisation's voice, held where the readings can hear it.
Review the record and its context before deciding what to do next.
Content → · Presence → · All manuals → · The Communication platform page →
Check your work
Choose the exchange type and intended recipients, attach the relevant work or event, and check visibility before sending. A read state records a system event; it does not demonstrate understanding or agreement. Use only appropriately scoped communication as evaluation evidence.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.