The job of this console
Coordinate in threads, then update the task or work item when the outcome is work. Do not treat unread chat as a backlog.
Project · Communication
Chat
Coordinate with teammates through threaded messaging and conversation panels.
Internal messaging with contact lists, group threads, and integrated header previews.
Threaded talk
Conversation next to delivery, not a second tracker
Chat is threaded messaging for teammates. Decisions that change scope still belong on the task; chat is the talk.
Projects · Chat
Route
/project/chat
Project team
Seat at the table
People on the project. Clients may be elsewhere (feedback).
The working rhythm
Open the conversation, reply, if work changed open the task and write it down.
Moments that bring you here
Unblocking. A quick design ping. After a board move that confused someone. When email should have been a task comment.
ⓘ
Talk is not Task
Chat does not create TaskActivity. Promote outcomes to the deliverable when they matter.
Overview
Chat provides workspace messaging for project coordination and quick context exchange.
Screen layout
Layout: Conversation list on left, message thread on right.
Entry points: Full chat page and header recent-threads dropdown.
Header & filters
Thread selection and search controls help narrow active conversations.
Summary & charts
Unread/recent indicators surface conversation activity; no heavy chart analytics on this page.
Main content & actions
Open thread, review context, post updates, and continue delivery coordination without leaving the workspace.
Complete feature list
Every control, panel, and workflow on this screen.
- ✓Luxury UI shellEmerald-themed glass cards, sticky gradient header, module sidebar, and responsive layout.
- ✓Documentation searchHeader search indexes all guide pages (docs site).
- ✓Channel listProject and team channels.
- ✓Direct messages1:1 conversations.
- ✓Thread repliesInline thread on messages.
- ✓AttachmentsShare files in chat.
- ✓Mentions@user notifications.
Before you start
💡
Kickoff channel
One channel per project; pin link to file-manager root.
📝
Notifications
Tune in HRMS Settings if mentions overwhelm.
Who uses this screen
Project teams communicating in channels and DMs — threads, mentions, attachments within Tracopus Luxury UI collaboration layer.
ℹ️
Team messaging
Use channels per project or workstream — decisions with lasting value should move to notes or file-manager.
Key concepts
Channel list
Project and team channels with unread badges.
Direct messages
1:1 conversations outside channel noise.
Thread replies
Reply in thread to keep channel readable.
Attachments
Share files inline — prefer file-manager for final docs.
Mentions
@user triggers notification per user prefs.
Permissions
| Role | Access on this screen |
|---|---|
| Project member | Post in project channels; DM teammates. |
| Project manager | Create channels; moderate if enabled. |
| Non-member | No channel access — DM only if org allows. |
| Guest | Limited channel invite on some deployments. |
📝
Administrator override
Org administrators and service accounts configured in the Admin console may bypass row-level scopes shown above. When in doubt, confirm access with your Tracopus administrator.
Controls reference
| Control | Description | Notes |
|---|---|---|
| Channel list | Switch conversations. | Unread counts. |
| New message | Compose bar. | Markdown subset. |
| Thread | Reply in thread. | Collapse in UI. |
| Attach file | Upload to message. | Size limit. |
| @mention | Notify user. | Respects mute. |
| Search in channel | Find past messages. | Date filter. |
| Create channel | PM action. | Link to project. |
Common mistakes
⚠️
Decisions only in chat
Lost after scroll — copy to pinned note.
⚠️
@channel abuse
Notification fatigue — mention individuals.
⚠️
Sensitive files in DM
Same retention as channels — use restricted file-manager folders.
FAQ
Chat vs email?
Chat for fast team coordination; client formal comms often email outside Tracopus.
Retention policy?
Org admin sets — may delete after N days.
Mobile chat?
Push notifications via mobile app if enabled.
Integrations?
Slack/Teams bridge org-specific.
Workflows
- Select contact or group.
- Review recent thread history.
- Post updates and action clarifications.
- Use full page for sustained collaboration.
Tips & best practices
Tip: Use project IDs in messages to improve searchability and traceability.
More guidance
💡
Remember
Project and team channels with unread badges.
ℹ️
Chat vs email?
Chat for fast team coordination; client formal comms often email outside Tracopus.