Overview
Asteria Engine collaboration chat keeps content discussions close to the posts, campaigns, and decisions they affect. It gives each workspace a shared place for campaign coordination, links, review context, and publishing updates.
Every workspace has its own chat context, which helps teams discuss the right brand, the right content, and the right publishing decisions without mixing conversations across clients or business units.
What Collaboration Chat Is Best For
Use chat when the conversation is broader than a single post note but still belongs inside the content workflow.
Typical use cases include:
- discussing upcoming campaigns
- clarifying content direction with the team
- sharing links and context around a draft
- coordinating reviews or approvals
- flagging urgent publishing changes
Use a post note for feedback about one specific post. Use collaboration chat when the discussion affects multiple posts, timing, or campaign direction.
Opening the Chat
Open the collaboration chat from the workspace interface using the chat entry point in the product navigation. The panel loads the workspace-specific conversation thread and can be closed when you want to return to the wider interface.
1. Select the speech-bubble Team chat button in the workspace header.
The important point is that the chat belongs to the current workspace. If you switch workspaces, you are switching the team conversation context as well.
Sending Messages Well
The raw mechanics are simple: type a message and send it. The more important question is what kind of message makes the workflow better rather than noisier.
Good chat messages usually:
- identify the content or campaign being discussed clearly
- say what decision is needed
- avoid vague comments like “not sure about this” without context
- distinguish between a real blocker and a preference
Teams that use chat well reduce confusion. Teams that use it badly create another layer of ambiguity.
Mentioning the Right Person
Use mentions when a specific person genuinely needs to respond, review, or act.
This is useful when:
- an Editor needs a Manager review
- a stakeholder needs to confirm a claim or CTA
- someone needs to respond before a scheduled post goes live
Do not overuse mentions for every routine message. If every post is “urgent,” nothing is.
Attaching Posts to Conversations
One of the most useful parts of collaboration chat is the ability to attach the actual post being discussed.
That matters because it reduces one of the most common workflow problems in content teams: people debating a draft in vague terms without everyone looking at the same asset.
When to attach a post
Attach the post when:
- feedback relates to a specific caption or creative
- approval is needed on an actual draft
- a teammate needs context quickly
- a revision request would be ambiguous without the post in view
If the team is discussing something concrete, attach the concrete object.
Threads and Message Structure
Use thread-style replies or structured follow-up where available when a conversation starts branching.
This helps when:
- several people need to comment on one draft
- a campaign discussion produces a side issue
- feedback should stay grouped under the original point
A clean discussion structure matters more as the workspace gets busier. Without it, the chat becomes searchable history but not usable working context.
Pinned Messages and Reusable Context
Pinned messages are useful when the team reaches a decision or shares information that will matter beyond the next few minutes.
Good candidates for pinned messages include:
- campaign direction that several people need to follow
- final approval criteria for a project
- a messaging rule that should stay visible
- important timing or launch details
Pinning should be used to preserve useful operating context, not to collect random historical messages.
Members and Visibility
Chat is a workspace-level tool. That means the right question is not only “can someone send a message?” but “should they be in this workspace at all?”
Use the members view and role model together:
- people who need only oversight may only need Viewer access
- Editors and Managers usually need clearer involvement in active discussion
- membership should still follow workspace discipline
For the permission model, see the Team Management Guide.
How Chat Fits With Approvals and Notes
Use chat for broad discussion
Chat is best for:
- campaign context
- team coordination
- scheduling decisions
- cross-post or cross-channel discussion
Use notes for post-specific commentary
Internal notes are often better for:
- exact revisions to one post
- issue tracking on a single draft
- comments that belong in the post history rather than in the wider team stream
Strong teams use both tools for the right reasons rather than forcing all conversation into one place.
Good Collaboration Habits
What makes chat useful
- attach the post when the feedback is post-specific
- mention the correct person only when action is genuinely required
- pin decisions that affect several people
- keep campaign discussions inside the relevant workspace
- move vague opinions into clearer decision language
What makes chat noisy
- discussing content without attaching the draft
- using the chat as a dumping ground for half-formed reactions
- overusing mentions
- mixing client or brand contexts in the wrong workspace
- treating chat as a substitute for actual approval discipline
Support Chat vs Team Chat
The workspace collaboration chat is for internal team coordination. It is not the same thing as any support or help widget used to contact Asteria directly.
Keep that distinction clear:
- use workspace chat for team communication
- use the support or contact route when you need product help, escalation, or troubleshooting outside the team workflow
Common Questions
Why can’t I see the chat?
Usually because one of these is true:
- you are not in the right workspace
- you have not been added to the workspace yet
- your session state is stale and needs refreshing
If access seems wrong, review your workspace membership first.
Can chat replace approvals?
No. Chat can support approvals, but it should not replace a clear review process. If the team needs formal sign-off, use the approval workflow as the control layer.
Should clients use chat?
Sometimes, yes — but only if their role in the workflow justifies it. Some clients are better as Viewers with visibility only. Others may need broader collaboration.
Recommended Next Steps
To use collaboration chat more effectively, pair this guide with:
Use collaboration chat to reduce ambiguity around content decisions, ownership, and next actions.