Portfolio Actions
Single-brand Actions answers "what's next on this brand?" Portfolio Actions answers the question that comes after: when you're operating ten brands at once, what's next full stop?
It's the same queue, the same action types, the same lifecycle (start, complete, dismiss, snooze, pin, reopen), the same trust spectrum where some actions are recommendations, some are drafts, and some Trakkr executes for you. The agency-specific layer is grouping, brand context on every row, and a brand filter sitting above it. If you've used single-brand Actions, the building blocks here will feel identical.
For the full model — how actions are generated, the trust spectrum, the lifecycle — read the Actions docs. Everything described there applies here, multiplied by however many brands you manage.
Grouping is the lever
The single most useful control on the page is the group-by dropdown. Four options, each suited to a different triage shape.
Time horizon (the default) splits the queue into Now, Up next, and Later. The right shape when you're triaging by urgency: what does my week look like, regardless of which brand is involved.
Brand turns each brand into a section. The right shape when you're working through one client's queue at a time, or prepping for a client check-in.
Category groups by the kind of work (setup, content, technical, citation, competitive). The right shape when you have a content day or a technical day and want to batch.
Action type is the agency-only superpower. If five brands all have a fix_meta_descriptions action, that's not five separate tickets — it's a portfolio-wide content sweep. Section headers surface the brand count ("Fix meta descriptions · 5 brands") so the pattern jumps out. Multi-select the lot, work through the drafts, ship them in one session.
Brand filter and brand context
The brand filter (chip-style multi-select in the toolbar) scopes the queue to one or more brands. It persists to the URL, so the filtered view is shareable.
Every row carries the brand's favicon and name without needing a column for it. With any grouping other than brand, the favicon is what tells you which client each action belongs to.
Acting on an action
Same as single-brand: the detail pane has the briefing, evidence, playbook, and any drafts. Transitions are start, complete, dismiss, snooze, pin, reopen. Bulk transitions work across brands (Complete attaches the right per-brand visibility snapshot to each). The page auto-advances to the next action after Complete or Dismiss so triage doesn't break stride.
For executable action types — CMS fixes, schema additions, content publishing — the inline executor and one-click apply work identically. There's no separate cross-brand approval flow.
When you'd use it
Daily standup. Default group (time horizon). The Now section is your day, Up next is your week. Work top to bottom.
Pattern-spotting across the portfolio. Group by action type. Section headers with brand counts tell you which work is portfolio-wide vs one-off. Multi-select the portfolio-wide ones, bulk through them in a single session.
Client check-in prep. Brand filter to the client's brands, status filter to Completed. You have the "here's everything we shipped" list ready to talk through. Switch to Open and you have the "here's what's next" list.
Plan access
| Plan | Portfolio Actions |
|---|---|
| Free | No access |
| Growth | No access |
| Scale | Full access |
| Enterprise | Full access |
Common questions
Why doesn't the synthesized briefing show up here?
The briefing is brand-scoped — it makes claims about that brand's visibility, citations, competitors. Stacking 15 briefings on one page wouldn't be readable, so they stay on each brand's single-brand Actions page. Click into the brand when you want the briefing.
Does dismissing here affect the single-brand queue?
It's the same record. Dismiss here, dismiss there. The two pages are different lenses on the same underlying queue, not separate queues.
What happens when the underlying signal resolves before I do the action?
The emitter retires the action automatically. A fix_audit_issue for a 404 disappears when the 404 is fixed, a get_listed_on_source disappears when the listing lands. The action just leaves the open queue.
Can I bulk-complete across multiple brands?
Yes. Select rows from different brands and the bulk transition runs against all of them, attaching the right per-brand snapshot to each one. Cross-brand bulk completes are the fastest way to close out a portfolio-wide sweep.