Your Booga Team
Corporate Agents workspaces arrive with a pre-staffed digital team: durable roles that wait for knowledge, connectors, and your go-ahead. Workflows are the jobs those roles perform. Smart Actions are how you ask for a job in plain language from the Assistant or the command pill.
Agents draft; people decide. Out-of-the-box roles start at Suggest or Draft, not fully autonomous.
Team roles
Every new corporate workspace can receive four dormant instances (inactive, autonomy disabled) until you activate them from the Team tab:
| Role | What it does |
|---|---|
| Researcher | Searches your knowledge base, synthesizes findings, and assembles a cited evidence package |
| Drafter | Retrieves context, assembles a draft from an approved Document Drafting template, and pauses for human approval |
| Monitor & Briefing | Triages incoming items, compiles briefings, distributes reports, and raises alerts — on a schedule or on events |
| Knowledge Steward | Profiles corpus health (coverage, freshness, extraction gaps, duplicates) and reports out |
These are roles, not one-off commands. Packs (legal, markets, general) add workflows on top of the same roles rather than adding new top-level agents.
The Drafter stays blocked until at least one active document template exists in Drafting Studio. Inferring a template is not enough — its status must be active.
Team tab and Agents landing
- Team (dashboard tab, just before Settings) is the role and activation surface: status, autonomy, health, readiness, and “what I need to start”
- Agents (default landing) keeps Active Automations and Pending Approvals at the top so approvals stay visible on first paint
Readiness inspects your corpus and connectors and proposes configuration (“we found contracts in these collections…”). Refresh readiness from the Team tab after a large ingest.
Activate a role
When readiness is activation-ready, use Activate on the card. That sets the instance active at Draft autonomy. Blocked cards deep-link to whatever is still missing. Already-active cards offer Manage in Agents.
Autonomy and approvals
Each instance has an explicit ladder:
| Level | Meaning |
|---|---|
| Disabled | Dormant — seeded default until you activate |
| Observe | Watch only |
| Suggest | Propose without acting |
| Draft | Produce drafts; typical out-of-box level after activate |
| Execute with approval | Side effects wait on a human |
| Autonomous | Not offered in the UI for default team activation |
Workflows that include a human-approval step pause until someone approves or rejects in the pending-approvals inbox. Rejection stops the run. You are notified when a request is waiting.
Smart Actions and the Assistant
Smart Actions are named jobs bound to public templates. They appear in:
- The Agent Command pill (bottom-left)
- Chat empty state / picker
- The Assistant tab: if you type a request that matches with high confidence, you get a propose card (action, extracted parameters, missing slots) instead of a normal chat turn. Approve, edit, or dismiss. Dismiss continues as ordinary chat. File attachments skip matching and go to chat.
On approve, the action runs (creating a durable instance for that template if needed) and a summary returns into the thread. If the agent needs approval, the card hands off to the Team / Monitoring approvals surface — there is no second confirm system.
Actions enforce the capabilities your plan includes. A denied action explains what is missing rather than failing silently.
Seeded Smart Actions
Availability depends on which templates and plan capabilities are present.
General
| Action | What it runs |
|---|---|
| Research the web | Web research report |
| Search knowledge | Cited report from your knowledge base |
| Analyze files | Structured insights from uploaded files |
| Analyze a pitch deck | IC-style investment memo with comparable-deal search |
Legal pack
| Action | What it runs |
|---|---|
| Find precedents | Precedent library + external legal sources (needs legal data access) |
| Draft an NDA | NDA from an approved Drafting template, with optional customer (needs document drafting) |
| Compare a contract | Incoming contract vs precedent clauses |
| Summarize client correspondence | Digest of attributed mail for a period; needs an active mailbox watch |
| Matter update | Briefing scoped to a matter’s knowledge categories |
Summarize client correspondence is a period digest. Client Correspondence Triage is a different workflow: bind a durable Monitor instance to new attributed mail (or unattributed mail as fallback) so each message is triaged as it arrives.
Markets pack
Requires financial data access. Most actions take a ticker; Market pulse does not.
| Action | What it runs |
|---|---|
| Research a stock | Profile, quotes, statements, estimates, news, filings → research brief |
| Compare to peers | Relative valuation vs the peer group |
| Prep for earnings | Calendar, consensus, beat/miss, last call |
| Check financial health | Quality-of-earnings style screen |
| Market pulse | Session snapshot: indices, movers, sectors |
| Earnings call changes | What changed between the last two transcripts |
Seeded agent templates
Besides the four team roles, the catalog includes workflow templates you can instantiate yourself.
Core and research
- Legal Document Processing Pipeline — extract, clause analysis, index, report
- Pitch Deck & Investment Memo — deck analysis and IC-ready memo
- Web Research Assistant — web search, summary, structured report
- File Analysis — extract, entity/structure analysis, insights report
- Knowledge Search & Analysis — semantic search plus synthesis
Legal pack workflows
- Client Correspondence Triage — one incoming email: what it is, whose matter, urgency, action
- Client Correspondence Digest — on-demand period digest (the Smart Action above)
- Precedent Search — firm library + external legal sources
- NDA Drafting — retrieve context → draft → human approval
- Contract Comparison & Clause Deviation Review
- Matter Brief & Weekly Matter Update
Markets pack workflows
- Equity Research Brief
- Peer Comparison Memo
- Earnings Preview
- Financial Health Check
- Market Pulse Brief
- Earnings Call Delta
Team-role templates are ongoing instances, not one-shot commands, so they are not seeded as Smart Actions.
Event-driven mail and legal intake
New Outlook mail can trigger agents when:
- A mailbox watch is running
- Event-driven automation is enabled for the tenant (Governance / automation settings)
- A schedule binds the workflow to mail received (or customer mail received for attributed mail)
The first mailbox import does not fan out one event per historical message. Customer attribution after that import is a backfill. Until event-driven triggers are on, a healthy sync can look complete while no agent runs.
Knowledge health
The Knowledge Hub can show a Knowledge Health panel driven by the Steward’s corpus profile: coverage, freshness, extraction gaps, duplicates. Use it to decide when to activate the Steward and when to fix unclassified documents.
Best Practices
- Land knowledge (index, collections, a few documents) before you expect Team readiness to go green
- Activate Researcher and Monitor first; activate Drafter after an approved, active NDA or other template exists
- Keep approvals on the Agents landing so they are not buried on Team
- Type Smart Action phrases close to the seeded wording (“Summarize new client correspondence this week”) for a reliable propose card
- Turn on event-driven triggers only when you intend mail to wake workflows
Troubleshooting
Team cards stay blocked
Problem: Readiness never reaches activation-ready. Solution: Open the card’s checklist. Typical gaps: no vector index, empty corpus, Drafter missing an active document template, missing legal or drafting capabilities.
Assistant chats instead of proposing an action
Problem: You typed a job but got a normal answer. Solution: Matching is confidence-gated and fail-opens to chat. Try the command pill picker, or a closer phrase. Attachments skip matching.
Mail arrived but triage did not run
Problem: Synced Mailboxes looks healthy. Solution: Confirm event-driven triggers are enabled and a mail event schedule exists. First imports do not emit per-message events.
NDA draft cannot pick a template
Problem: The Drafter or Draft an NDA action has an empty template list. Solution: In Drafting Studio, the document template’s status must be active, not only a finalized draft document. Status is separate from finalizing a generated Draft.
Related Topics
- AI Agents — User Guide
- Document Drafting Studio — User Guide
- Customers and Clients — User Guide
- Synced Mailboxes — User Guide
Related Topics
⏱️ Read time: 16 minutes | 📊 Difficulty: intermediate | 🔄 Last updated: 2026-08-30