Team Chat
Team Chat is internal teammate-to-teammate messaging inside a Woes workspace. It is separate from customer-facing live chat: customers never see Team Chat messages, and Team Chat does not create customer support conversations.When To Use It
Conversations And Channels
Team Chat supports two conversation types:
Public channels can be discovered and joined by workspace members with Team Chat access. Private channels require membership. Archived channels are read-only until they are restored.
Core Actions
Operators can:- Start or continue DMs.
- Create channels.
- Browse and join discoverable channels.
- Leave channels where they are a member.
- Archive or unarchive channels when permitted.
- Manage members in channel settings.
- Send, edit, and delete their own messages.
- Add emoji reactions.
- Attach files to messages.
- Mark conversations read.
- Click a teammate name in a thread to view their profile popover, email them
with a
mailto:link, or start a direct message when allowed.
Permissions
Team Chat respects workspace permissions and membership checks.
If a user does not have Team Chat access, Woes shows an access state instead of the chat surface.
Presence And Realtime
Team Chat uses the same workspace realtime presence foundation as the rest of Woes. While Team Chat is open, teammates can appear online, idle, or recently active. Realtime subscriptions update messages, reactions, attachments, membership, read state, and channel lists without requiring a refresh. Presence is operator context, not authorization. Route handlers still enforce workspace membership, channel membership, and per-action permissions.Attachments And Reactions
Attachments are linked to Team Chat messages and remain internal to the workspace. Reactions are scoped to the conversation and update live for everyone who can view the thread.Route Boundaries
Team Chat uses authenticated workspace routes under/api/team-chat/*. These routes require a signed-in Woes user session and do not accept public widget keys or woesk_ REST API keys.
Common route families include:
Safety Notes
- Team Chat is internal to workspace operators.
- Team Chat messages are not customer-visible.
- Customer widget credentials do not authorize Team Chat routes.
- Workspace API keys do not authorize Team Chat routes.
- Channel membership and workspace tenant checks apply to every request.