The agency runs its own tasks on the same hub

The builders' task hub pointed at the agency's own reserved account — same composer, same reminders, same calendar, assigning to staff instead of crew.

What it is

A scope provider makes every task call carry an org marker, so one component serves both a builder's tenant and the agency itself. The agency panel mounts it inside a collapsible Tasks section.

Also called: platform tasks · internal team tasks · agency to-do list

See it
The agency runs its own tasks on the same hub
Apr
May
Jun
Jul
Ronan Petsch — Barndominium
Framing
Gideon Alt — Riding Arena
Concrete
Ivy Brubaker — 30×40 Garage
Trim
Marlin Hoover — Hobby Shop
Framing
Delia Yoder — Barndominium
Concrete
Framing crewConcrete crewTrim crew
The agency panel's Tasks section with the familiar hub inside it, full width. platform/page.tsx. Sample data — no customer information appears here.
How it works
  1. 1A React context decides whether task API calls carry the platform scope; the default is the signed-in user's own tenant, resolved server-side.
  2. 2The API gates the platform scope behind a platform capability and swaps in the agency org id.
  3. 3Recipient resolution for the agency account reads the platform staff roster instead of org members, so the agency's own reminders reach its own people.
Why we built it

Recorded in both the scope file and the API: the same TaskHub and TaskComposer the builders use run for the agency itself, so the agency 'reminds its own people the same way'. Building a second task system for internal use would have doubled the surface for no benefit.

The problem
  • A separate internal tool drifting from the product
Sound familiar?
What you get
One codebase, two audiences
Every improvement lands for both at once

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →