Short guide for workspace admins and power users. End users mainly need: select boards → View checklists → use Refresh day to day.
| Action | What it does |
|---|---|
| Board catalog (automatic) | Fetches open board names on open |
| View checklists | Pulls checklist items from selected boards |
| Refresh | Refreshes current work and adds newly selected boards |
| Rescan selected boards | Finds brand-new assignments on boards already loaded |
| Select / deselect Boards | Controls which boards contribute visible work |
Completing work always happens on the Trello card (Power-Up is read-only).
Create a checklist named exactly:
Checklist Hub Team: {Team Name}
Example: Checklist Hub Team: Content Ops
| Item type | Meaning |
|---|---|
| Assigned to a member | That person is on the team (Assignees preselect) |
| Unassigned, text = board short link or URL | Board included when that team is chosen |
Board links can be:
AbCdEfGh)https://trello.com/b/AbCdEfGh/...)If a team has no board links, users can still select boards manually. Prefer adding board links so Quick start is one click.
Anyone can save the current filters / boards / grouping from Filters → Saved views.
Views are per browser / host cookie, not shared workspace config. For a shared “starter”, document a recommended view name and have each person Save it once, or rely on Teams for shared board/people scope.
When teams and/or saved views exist, welcome shows one control:
Then View checklists (button label adapts). Don’t show again hides welcome on future opens; How refreshing works (in Filters) brings it back.
demo.html and top-level dashboard.html use the built-in mock dataset so people can try filters/views without authorizing. Demo data is intentionally kept wired in the dashboard bundle.
public/ on HTTPS; set the Power-Up connector to that origin.config.js is expected client-side for Power-Ups; set Allowed Origins; never commit personal member tokens.public/_headers; other hosts need an equivalent header.demo.html works offline from Trello