Workspace

Inbox

One unified place for every project conversation — client messages, internal notes, and task comments — so nothing slips through and you can reply without jumping between projects.

What shows up here

• •Client messages — replies from clients in their portal threads
• •Internal threads — private team chats per project (clients never see these)
• •Task comments — comments left on tasks across all your projects

Unread items are highlighted at the top with a coloured dot. Clicking an item opens the full thread on the right and marks it read — which also clears the matching notification on your bell, so the two counts always agree.

Needs reply

The inbox opens on Needs reply: every conversation where the client spoke last and you haven't answered yet. It's the shortest possible answer to “is anyone waiting on me?” — work it to empty and you're done for the day.

• •Needs reply — client-last conversations, oldest pressure first
• •All — every conversation and comment across your projects
• •Notifications — your unread workspace notifications in the same place

Each row carries a chip linking straight to the project, client, or task it belongs to — click the chip to jump to the source, or click the row to read and reply.

Searching

The search bar matches against project name, client name, sender, and message body — type a few words to jump straight to a conversation.

Replying inline

Reply directly from the inbox — no need to navigate to the project. You can reply from the list row itself for a quick answer, or open the conversation for the full thread. Replies are sent as you, the team member; clients see your name and the workspace branding in their portal.

Writing a message

The message box is a proper writing area, not a single-line input — it starts several lines tall and grows as you write, so a paragraph looks like a paragraph while you type it. The same composer is used everywhere messages are written: project Messages, client Messages, the inbox reply, and the client portal.

• •Formatting is there from the start — bold, italic, underline, bullet lists, and numbered lists. The toolbar is visible by default; the formatting button in the footer row collapses it if you want the room back.
• •Enter sends. Shift + Enter starts a new paragraph — so a multi-point message goes as one message instead of five pings.
• •Paste an image straight in — copy a screenshot and hit paste. It uploads and attaches like any other file.
• •Drag and drop a file onto the composer, or use the paperclip. Attachments are stored as files against the project, not stuffed into the message body.

Starting a conversation

From a project's Messages tab (or a client's), you start a conversation by writing the message. The subject line is optional: leave it blank and the subject is taken from your first line. The conversation and its first message are created together, so a subject on its own can never leave you with an empty thread — and if sending fails, nothing is created and your text stays in the box ready to try again.

A project's Messages tab has two lanes — Conversations (the client can see these) and Internal (team only). Start the thread from the lane you want it in; internal notes never appear in the client's portal. Pressing Enter in the subject field moves you to the message rather than sending, because a subject on its own is never enough to start a conversation.

Why use the inbox?

Without it, project messages live scattered across each project page. The inbox is the "is anything waiting on me?" view — open it once a day, clear what needs replies, and move on.