Define your operating context
Set tenant profile, core product lines, regions, and the teams that should receive routed work.
Workspace
Configure how this tenant automates, who owns rollout decisions, and which guardrails apply before workflows can act.
Setup Walkthrough
Treat setup like a guided rollout. The platform becomes more useful with each connector and each policy decision you enable.
Progress
0/7 connectors connected
Set tenant profile, core product lines, regions, and the teams that should receive routed work.
Each connector gives the platform more context and more ways to complete work on your behalf.
Start from the workflows you want completed, not from which department owns the task.
Pick what should draft only, what should require approval, and what can safely auto-run.
Begin with transcript-first workflows, CRM hygiene, follow-ups, and launch asset orchestration.
Connector Capability Map
Content
Use asset metadata and templates so decks and collateral updates stay on-brand.
Unlocks: Confirm asset workflow and service account approach
Engineering
Create issues, inspect repositories, and later stage draft pull requests with explicit approval gates.
Unlocks: Approve repo allowlist and install GitHub app
Productivity
Link calendars, docs, and drive content so workflows have richer business context.
Unlocks: Connect admin account and enable document indexing
Meetings
Capture meeting recordings, transcripts, and chat context for enterprise customers standardized on Microsoft 365.
Unlocks: Connect Microsoft 365 tenant and approve Graph permissions
CRM
Sync accounts, opportunities, contacts, and forecast changes into the shared work graph.
Unlocks: Start OAuth and map opportunity fields
Collaboration
Capture channel context, notify teams, and route approvals and summaries into the right rooms.
Unlocks: Install workspace app and approve channel access
Meetings
Import recordings and transcripts so meetings can trigger follow-up workflows automatically.
Unlocks: Connect org account and enable meeting webhooks
Automation Posture
Start conservative, then move into deeper automation once connector coverage and approval routing are trusted.
Setup Area
Map medium and high-risk actions to the right approvers by team, region, or account ownership.
Setup Area
Choose whether the platform only observes, drafts work for review, or auto-executes low-risk tasks.
Setup Area
Enable integrations in the order that gives the biggest impact with the lowest setup burden.
Setup Area
Company identity, product lines, regions, and business unit defaults used for routing and permissions.
Guardrails
Draft PRs and code changes remain disabled until repo allowlists and review chains are set.
CRM updates, outbound notifications, and connector mutations require explicit policy checks.
Internal summaries, draft docs, and workflow suggestions can run automatically.
Raw meeting data stays restricted to the account team, participants, and delegated reviewers.
Outcome Library
Teams: Sales, RevOps, Success
Teams: Product, Engineering, Field
Teams: PMM, Marketing, Enablement
Teams: Success, Marketing, Product
Teams: Executive, Ops, Finance
Teams: Security, IT, Support, Solutions Engineering