A shared board a manager can trust.

• Marking a task done waits 60 seconds before it counts, with an undo toast
• Bulk archive shows one toast for the whole batch
• Stage actions wait out a 60-second window you can cancel before they run
• The undo toast is announced to screen readers

Every board has owners, editors, viewers and contributors. A contributor can add tasks to a board they cannot open, so a rep can file work without seeing everyone else's.

• Per-stage viewer lists and a per-user create, read, update, delete matrix
• Admin-only stages
• Team oversight: admins and a team's manager can see and act on members' private boards
• Creating a board needs permission

• Activity log written by the database, not the browser, per task and per board
• Audit export: a CSV of the activity log for any date range, guarded against spreadsheet formula injection

The objection to putting a team on one board is always the same, and it is a fair one: if everybody can move everybody's work, somebody will move the wrong thing. Usually on a phone, usually in a hurry, usually on the job that mattered.

So the answer is not to lock the board down until it is useless. It is to make a mistake cheap. An action that waits before it counts can be taken back by the person who took it, without a message to the office. A log the database writes — rather than the browser asking nicely — means the question "who moved this?" has an answer that does not depend on anyone's memory. And roles mean a rep can file work into a board they were never meant to read.

That is the trade this page describes: a board open enough that the people doing the work actually use it, with enough of a record that the person answerable for it can sleep.