Marketing Hub
Use Marketing Hub to keep the marketing work you care about in one workspace
view. Ask the Breyta agent to add tabs and cards from your sources, Storage
files, flow outputs, and suggested next actions.
What You Can Ask For
Examples:
- "Build a Home tab with this week's runs, success rate, and next actions."
- "Add an SEO tab with a rank table and the latest content brief."
- "Show the latest campaign output without making me open the run."
- "Add a campaign gallery from these Storage results."
- "Put our current initiative and Friday checkpoint at the top."
- "Remove this card and undo the last dashboard change."
The Hub supports:
- metrics
- tables and charts
- artifacts and latest successful outputs
- Markdown notes and narratives
- marketing suggestions that you can approve, discuss, or dismiss
How Changes Work
The workspace agent is the dashboard editor.
- Tell the agent what outcome you want.
- The agent reads the current dashboard and the available card catalog.
- It preserves unrelated tabs and cards.
- It applies your requested change.
- The Hub refreshes while the persistent chat remains available.
Direct requests can be applied immediately. If the agent has an idea you did
not ask for, it should explain the idea and wait for your confirmation before
changing the dashboard.
First Setup
An empty workspace does not create a dashboard automatically. After the
workspace has a useful source, run, or marketing suggestion, Breyta can create
the first Home tab through an authenticated, idempotent browser action. An
explicit UI Chat or CLI request can create the first dashboard sooner with
revision 0.
Page reads and live update connections never create or repair dashboard state.
Tabs And Live Data
Only the selected tab loads its connected data. This keeps dashboard work
bounded even when the Hub has several tabs.
For latest-output cards:
- Breyta uses the exact flow and run profile selected for the card.
- The last successful result stays visible if a newer run fails.
- The card shows that the result is stale without exposing provider errors or
internal run details.
Connected run, flow catalog, and dashboard changes refresh live. Use Refresh
for other connected resources when needed.
Email A Tab
On a populated tab, open Share:
- Create email update prepares a one-off report.
- Schedule weekly email prepares a recurring report and schedule.
Both options place a detailed request in UI Chat for you to review. Nothing is
sent, submitted, or scheduled when you click the menu item.
The agent checks your email connection, builds the report from the tab's
underlying sources and outputs, and shows the exact email before sending. A
weekly report rereads those sources each time and stays disabled until you
approve the recipients, sender, subject, HTML, day, time, timezone, and failure
behavior.
Email updates can include metrics, HTML tables, and safe links to reports or
outputs. Graphs remain available in the linked report or Hub in this first
version; they are not attached as chart images. Workspace links may require
sign-in. External emails contain no links unless you explicitly approve a
public share and its expiry.
Collaboration And History
The dashboard is shared between the workspace creators and admins who use the
Hub.
- Creator and admin members can change, undo, and restore it.
- Existing role-based home routing is unchanged. Marketing Hub does not add
Overview access for buyer roles. - Suggestion cards are resolved for the person viewing the Hub.
History keeps the latest 50 dashboard revisions. Restoring an earlier layout
creates a new revision, so newer history is not deleted.
Safety
The agent chooses from a fixed component and action catalog. A dashboard cannot
store or execute arbitrary JavaScript, browser handlers, React components, raw
web URLs, or viewer-specific suggestion ids.
Storage and output cards still use normal workspace authorization. A resource
from another workspace cannot be attached by changing the dashboard
configuration.
Agent Command Reference
The authenticated workspace-agent CLI surface is:
breyta agent dashboard show --prettybreyta agent dashboard catalog --prettybreyta agent dashboard apply --expected-revision <revision-or-0> --manifest-file <path> --change-summary "<summary>"breyta agent dashboard history --limit 20 --prettybreyta agent dashboard restore --expected-revision <current-revision> --revision <revision> --change-summary "<summary>"
Dashboard writes use the latest expectedRevision. When show reports
bootstrapRequired: true, revision 0 creates the first dashboard directly
from the terminal. It fails with a revision conflict if another collaborator
creates the Hub first. For every later write, the agent must reread, merge, and
retry rather than overwrite newer work.