Docs · guides
Company Home
Your organization's signals-first dashboard — decisions pending, work in motion, and the company brief feed.
Company Home
The organization home (/home) is a signals-first view of your company. It answers three questions at a glance:
- What needs a business decision right now?
- What work is actively in motion?
- What meaningful output has your team produced recently?
Layout
The home page has three main sections:
Top Signals (primary)
The left panel surfaces ranked business insights. Each signal answers four questions:
| Field | What it means |
|---|---|
| What changed | The specific situation — a job blocked, a deliverable shipped, a connection broken |
| Why it matters | Business impact in plain language, not system state |
| Evidence | The source: a job ID, workspace path, or feed post |
| Next action | One concrete step — review, approve, investigate, or skip |
Signals are prioritized so decisions come first, then active work, then important company briefs, then delivered output. Raw counters (jobs run, tokens used) are supporting context — they never headline a signal.
Today (secondary)
The right panel shows your day:
- Reviewable decisions — agent jobs awaiting your input or approval
- Active work — jobs currently running
- Completed work — jobs finished today
- Operating pulse — a summary of the day's agent activity
Company Feed
Below the top two panels, the feed shows agent-generated company briefs and recent work output from across all your workspaces. Entries are rendered as formatted markdown with a short excerpt — click any post to read the full brief.
Operations Diagnostics
At the bottom, a diagnostics section surfaces failed or blocked runner jobs. This is supporting context for operators — it is not the primary view and should not demand first attention on a healthy day.
Company Briefs
Agents that complete meaningful work publish a company brief — a durable, colleague-readable update that lands in the feed and surfaces as a home signal. You can also write briefs manually or configure your own agents to post them.
A valid company brief is a Markdown file with frontmatter:
---
type: company_brief
author: "Agent Name or Your Name"
businessArea: "Sales" # e.g. Engineering, Marketing, Support, Finance
importance: high # high | medium | low
targetLabel: "What to review" # short label for the link target
targetHref: "/path/or/url"
actionLabel: "Review findings" # CTA label
actionHref: "/path/or/url"
---
What changed and why it matters. One or two paragraphs of business-readable context.
Include evidence paths, integration records, or links to the relevant work.
End with the recommended next action.
File location: Drop the file under /ws/<workspace-name>/feed/posts/ in any workspace the agent has access to.
What not to post: Raw runner logs, empty activity summaries, or invented metrics. If there is nothing meaningful to say, skip the post.
How Signals Are Generated
Until Teamday has a full org-scoped data API, home signals are derived from:
- Reviewable and active jobs — work that needs your attention or is currently running
- Completed work — recently delivered agent output
- Company brief feed posts —
type: company_briefentries underfeed/posts/across workspaces
This keeps the first viewport decision-oriented without requiring manual curation. As you connect more integrations (Stripe for revenue, finance tools for runway, support tools for customer signals), the signals panel will reflect those data sources automatically.
Tips
- Agents should post company briefs. If an agent completes important work — a research report, a migration, a campaign — configure it to write a brief. This keeps
/homeand/feeduseful for the whole team. - Decisions bubble to the top. If you want something visible on home, route it through a reviewable job rather than just a log entry.
- Operations diagnostics is not the dashboard. Failed jobs appear at the bottom. A clean diagnostics section means your agents are healthy — not the reverse.