Skip to main content

​
Kanban

Kanban is the core production workflow — boards made up of lanes and cards, plus everything attached to a card: steps, comments, contacts, documents, and review. You can browse a list of your boards, or open a specific board to see it in full.

​
How boards are organized

  • Boards → Lanes → Cards. A card’s overall status (Not Started, In Progress, Complete) is based on where its lane sits relative to the first and last lane on the board.
  • Card types — article, news, video, photo, graphic, social, podcast, comms, and web. Each board can enable, disable, or rename the types it uses, and mark specific types as publishable.
  • Lanes can be set to sort their cards automatically — by deadline pressure, newest or oldest first, or readiness — or left to manual ordering. A lane can also be marked as a review lane with a default reviewer.
  • Cards can relate to each other — as parent/child, as a bundle of related items (hidden from the board by default until you need them), or connected laterally to something unrelated.
  • Steps are checklist or handoff sub-tasks on a card, optionally scoped to a specific lane, and can be loaded from a board’s workflow templates.

​
What you can do

  • Drag and drop cards between lanes (Viewers can’t do this).
  • Create a card, claim an unassigned one, or assign and reassign it.
  • Comment on a card, view its history, and restore it from archive or trash.
  • Manage board membership, transfer ownership, view analytics, and export card history to CSV.
  • Pass or boomerang a card to another board — “pass” hands it off outright (the receiving board can accept or decline it), while “boomerang” sends it away with the expectation it comes back, and you can recall it yourself if needed. While it’s away, it shows up as a limited placeholder on its home board.
  • Review workflow — a card sitting in a review lane shows its reviewer an Approve / Request Changes option.
  • Internal Pitch Pool — a board-scoped queue for pitching a card idea onto the board, separate from the public intake forms covered in Portals.
  • Board Library — reference links scoped to the board, the same mechanism Hub’s library uses.

​
Good to know

  • Board-level roles (Owner, Editor, Creator, Viewer) control what you can do — see Board Roles. Creating a new board is limited to Admins and Managers.
  • A campaign Lead can add a card directly onto a board they aren’t otherwise a member of, as part of that campaign — see Campaign Roles.
  • Moving a card between lanes can trigger automatic follow-through: notifying the assignee, assigning a review lane’s default reviewer the first time a card enters it, notifying a parent card when a child’s status changes, returning a boomeranged card to its home board once it’s done, and advancing a bundle once its last item finishes.
  • Confidential cards are only visible to their creator, the board owner, and the assignee — enforced consistently, including on Calendar.
  • Boards can be set to auto-archive cards after a set number of days; permanently deleting from trash is Admin-only.

​
Connections to other features

Cards show their campaign, and campaign leads can seed cards across boards as noted above. A card’s contact links use the same Contacts data available elsewhere. Portal management for the board lives here too — see Portals. Publishing a card can trigger AEO scoring — see the Intelligence Pack. Cards also carry fields specific to comms/higher-ed work, like college or department and funding details.