DISCUSSIONS · PROJECT COMMUNICATION
The conversation stays part of the project.
Discuss project questions in context — right where the data, files and decisions already live.
- Source contextReturn from the topic to the object where the question started.
- Personal work feedInbox, mentions, reactions, unread items and reminders collect what needs attention.
- Recorded decisionThe conclusion, attachments and history remain after the question is resolved.
CORE WORK CONTEXTS
A discussion starts where the question appears.
PDF · point and text description
Tasks · task and execution
Documents · file and version
Finance · document and payment
Inventory · procurement, asset and movement
CRM · client, deal and card
WORKSPACE
One entry point for every discussion you can access.
Discussions collects topics and messages from different work contexts without losing their origin: every message still belongs to a topic, source and access boundary.
Quick views change only the presentation. They show messages from topics the user is already allowed to open.
SOURCE RELATION
A topic keeps a path back to the object where the question started.
The team discusses the working object without creating a copy in a separate chat. The source remains the system of record; Discussions keeps the conversation and decision history.
DISCUSSIONS
Topic · messages · decision
-
ProjectBase / PDFRecord, field, relation, drawing point or text description.
-
Tasks / DocumentsTask, document comment and file version.
-
Finance / InventoryFinance document, payment, procurement, asset or movement.
-
CRM and other contextsClient, deal, room, table, module or free topic.
INBOX & SEARCH
Find both the conversation and the exact point inside it.
Search answers “where did we discuss this?”, while activity views answer “what do I need to process now?”.
-
01
Inside a topic or across accessible topics
Search by text, author, topic, module, date range, attachment, reaction, star, mention or pinned message.
-
02
Inbox as an attention queue
New messages and events are collected automatically; unsubscribed topics and channels do not add unnecessary noise.
-
03
Open the exact message
A search result opens the related topic around the matched message; unread state helps you continue from the right place.
KEY MESSAGE ACTIONS
A working message stores more than text.
These are the main actions that preserve context, help you return to what matters and record a decision inside the topic.
Attachments and images
A file remains part of a specific message and is available to topic participants with the required access.
Mentions
Bring a specific participant directly to the place where their reply is needed.
Quotes and linked objects
A reply can keep a quote, a topic link, a ProjectBase record or another supported object reference.
Reactions
Confirm reading, agreement or the need to check without adding another short message.
Star
Build a personal list of important decisions, links, files and wording.
Reminder
Set a reminder on a specific message and return to it later.
Pin
Keep a conclusion, important file or instruction visible to participants in a long topic.
Send to project notes
A selected message fragment can be saved to project notes when the context supports it.
Drafts and send later
A draft is restored per topic, while a scheduled message can be edited or cancelled before it is sent.
FROM QUESTION TO DECISION
The question closes. The history does not disappear.
Discussions separates the conversation from the topic state and preserves why the team reached a decision. Resolved and archived are different states.
-
01
Open a topic
The question appears next to its source object or as a free topic in a broader context.
-
02
Discuss
Participants add messages, links, files, mentions and reactions.
-
03
Write the conclusion
The agreed decision is recorded as a clear standalone message.
-
04
Pin what matters
The key answer stays visible inside a long topic.
-
05
Mark resolved
Resolved closes the question without deleting messages. Archive the topic separately if it no longer belongs in the normal working list.
REALTIME
When realtime is available, changes appear without a manual refresh.
New messages, reactions, counters and state changes can synchronize for participants who have access to the topic.
New reply
A message can appear in the open topic without reloading the page.
Attention signals
Unread, mentions and related counters update with the working feed.
Topic state
Participants can see the current question state and new reactions.
Realtime does not bypass ACL: events are available only to users who are allowed to read the corresponding topic and its context.
ACCESS
A discussion does not widen access to the working object.
Topic visibility starts with access to the project and resource; a closed topic adds an explicit participant boundary.
OPEN
Open topic
It is visible to users who already have access to the corresponding project and topic resource.
01ACL
02Open topic
CLOSED
Closed topic
It remains part of the project but, inside the allowed resource boundary, only selected participants can see it.
01ACL
02Closed topic
Inbox, search, mentions and other personal views show only topics the user is already allowed to open.
DISCUSSION ≠ TASK
Decision and execution are different entities.
A topic answers “what did we decide and why?”. A Task answers “who does it, by when, and is it complete?”.
Discuss and recordAssign and track
The question, options, materials, messages and agreed decision stay in Discussions.When a decision gets an owner, deadline, work plan or completion tracking, it belongs in a Task.
SYSTEM MESSAGES & INTEGRATIONS
Service changes remain part of the topic history too.
Discussions shows system rows for important topic actions and can accept system messages from external integrations through a webhook.
DISCUSSIONS
Messages · states · system history
-
Resolved / reopenedA change to the question state is recorded as part of the topic history.
-
Archive / restoreArchiving and restoring a topic do not erase its previous messages.
-
Message movedThe source and destination topics keep a system trace so the conversation does not lose context.
-
Webhook eventAn external service can add a system message to an existing topic with its own event source.
FAQ
Discussions boundaries
What a topic stores, where access comes from, and when a Task is needed instead of a discussion.
Is this just a project-wide chat?
No. A topic can be linked to a specific working object such as a ProjectBase record, PDF point, task, document, finance, inventory or CRM context. A free topic is useful for a broader question that is not tied to a specific object.
Why might a colleague not see a topic?
An open topic requires access to its project and resource. A closed topic additionally requires the user to be an allowed participant. Mentions, search and Inbox do not bypass these limits.
What remains after Resolved?
Messages, attachments, links, reactions, the final decision and source context remain available. The question state changes, not the topic history.
Can we find an old decision later?
Yes. Search works across accessible topics and messages, while starred and pinned messages make important material easier to return to.
How is a Discussion different from a Task?
A Discussion stores the conversation and agreed decision. A Task is needed when there is an owner, deadline, work plan or completion tracking.
What happens to drafts and scheduled messages?
Drafts and scheduled messages remain private until sending. A scheduled message can be opened, edited or cancelled before it is sent.
DISCUSSIONS
Connect conversations to the objects where the team actually works.
We will review current chats, comments and work modules, identify the right Discussions contexts and build a clear path from question to decision.
Start with one process, such as ProjectBase, PDF or Tasks.