User guide

Collaboration

The other half of the product. backendup does not bolt a chat window onto a tracker: the conversation and the work are the same records - every work item, project and feedback entry carries a discussion, and the Collaboration tab gathers all of them, plus channels and direct messages, into one living workspace.

live, not polling threads attached to work notifications you control

One system, two homes

You can meet a conversation where the work is - the thread under a story's work item page - or in Collaboration, the app you switch to from the top navigation. It is the same thread either way: a comment posted in one appears in the other instantly, and the unread badge on the Collaboration tab counts everything waiting for you across both homes. Messages arrive over a live connection, so an open workspace updates as people type and post - if the socket drops, you will see Connecting live updates… rather than a silent gap.

The workspace layout

The left rail lists your conversations the way you organize them: Pinned at the top, then Team channels, Project discussions, Direct messages and Group messages, with folders interleaved. The rail's own views answer different questions: My messages (everything you have said), Mentions (everything aimed at you), Notifications, Shared with me, and Notes to self - a private scratch conversation only you can post in.

Channels

Three kinds, created from the rail's New… buttons:

  • Team channels span an organization - or, for admins, the whole team with All active team members - and are created or resumed rather than duplicated.
  • Custom channels are organization-scoped spaces for a chosen audience: everyone, all visible projects, or a selected list of people you add.
  • Project discussions are the channels wired to projects you can see - the place a project talks. Work items under it carry their own threads, one level deep, so a discussion can branch into replies without fragmenting.

Channels you no longer need are archived, not destroyed; finished projects keep their conversations in a Finished projects view.

Direct and group messages

New direct message opens a person as a draft - or resumes the chat you already have with them, because a person only ever has one DM thread. New group message gathers selected people into a private group you can rename and leave (Leave group). Both behave like channels: live, searchable, attachable.

Writing messages

The composer is the same everywhere: markdown with a Formatting shortcuts cheat sheet, @name mentions that notify, emoji reactions, and replies to a specific message. Drop files to attach works by dragging files onto the pane. Drafts are saved as you type - leave mid-sentence, come back, the half-finished message is waiting. After sending, you keep authorship: Edit rewrites a message and History shows every revision; Forward copies it into another conversation with its origin attached. Search discussion messages covers the current channel, and the global search bar covers everything.

@channel and @here: addressing the room

@channel is a broadcast, not a courtesy tag: it notifies every member of the conversation at send time - on a team channel that audience is the whole organization. @here narrows that to the members presence saw active right now, snapshotted at the moment you send - and it is deliberately brittle-proof: if the presence service is unavailable, @here is refused with an explanation rather than quietly becoming an @channel that pings everyone offline. @here also never produces email at all - mail would reach people who were not here. The composer autocompletes both tokens, and before the message leaves you confirm the real addressee count. @channel broadcasts never send anyone an individual instant email: everyone addressed gets the notification-center entry and a live banner, and the email arrives merged into the next digest run - quiet hours included, so a large announcement cannot burn the organization's daily mail budget. Two dials govern who may broadcast: the organization's who-can-broadcast setting (all members by default, or owners and admins) with a channel override that can only tighten it, plus an automatic owner/admin restriction above a configurable size threshold (15 addressees by default; @here counts the active members it would address). A refusal always names which rule stopped you. Editing a message to add a token is treated as a fresh broadcast - same audience, same gate, same digest rules - while an edit that merely keeps an existing @here never re-pings whoever happens to be online now: the snapshot taken at the send stays the audience it described. Automation posting through the API or a channel webhook passes the identical gate with its credential badge visible.

Your own right of reply is the receiver switch. Every channel's notification menu carries Include @channel/@here (on by default): turning it off means a broadcast there no longer lights your notification center - while the message still counts unread, everything else about the channel keeps working, and a person-level @name mention always reaches you regardless (different token, different promise). Organization managers can set the culture for the future: with the receiver default switched to opt-in, channels created from then on hold broadcasts until each member includes them - existing channels and personal choices are never rewritten.

Reading, when there is too much

Unread state is yours to manage: Mark conversation read clears a whole thread, while Mark unread from here puts it back on your plate when life interrupted. Folders keep the rail honest - New folder, drag conversations in, Rename folder, Collapse all / Expand all / Expand unread for the whole tree at once, and Keep in both when a conversation belongs to two groups. Pinned channels stay at the top of the rail in the order you arranged them.

Notifications: three levels, four doors

Per conversation and per channel, choose Follow (all messages), Mentions only, or Mute. Watching a work item or project adds you to its participants, so its discussion reaches you even without a channel. Then pick the doors the notifications come through, in your profile settings:

  • In the app - the badge, the Notifications view, and live updates in any open workspace.
  • Browser alerts - "Receive browser alerts, including when backendup is closed. Your browser will ask for permission." These are push notifications, not tabs you happen to have open.
  • Immediate email - "Send an email immediately for new discussion notifications."
  • Email digest - "Receive unread discussion notifications in a scheduled email digest" - for people who would rather batch the noise than delete it.
  • Quiet hours - weekday and weekend windows in your own timezone hold those doors shut while you are away: mail merges into the next digest, browser alerts park until the window ends, banners stay silent - and every message still arrives and counts. Pause-until buttons on the Notifications view do the same for one stretch.

Keep going