HubSpot integration

What Management OS does with your HubSpot data.

Operator-grade transparency. Every OAuth scope we request maps to a specific Management OS feature you can see and measure. Nothing pulled, nothing stored, nothing inferred beyond what this page documents.

1. What we read

Management OS reads CRM data from your HubSpot instance — specifically: companies, contacts, deals, and sales-email engagement events. We do not access email body content, attachments, marketing campaign data, service hub tickets, CMS pages, files, or any HubSpot data not explicitly listed in the scope table below.

Why: Management OS is the leadership execution layer above the revenue stack. We synthesize CRM data into a Weekly Intelligence Brief that develops the leader, their team, and their business. We can't synthesize what we can't read.

2. What we write

We do not write to your HubSpot CRM. Management OS is a read-only consumer of your HubSpot data. We do not create, modify, or delete any HubSpot records — no companies, no contacts, no deals, no notes, no activities, no properties, no workflow triggers.

All Management OS outputs (Account Plans, Coaching Briefs, Forecast Locks, Meeting Prep dossiers, Pitch Decks) are generated and stored in Management OS's own database and surfaced through the Management OS application — not pushed back into your HubSpot instance.

3. The OAuth scopes we request — and why each one

Every scope below maps to a specific feature. We requested the minimum scope set needed to deliver the Management OS feature surface; we did not request scopes that we don't currently use.

Required scopes (5)

These scopes are requested on every connection. Without them, the core Management OS feature surface does not function.

oauth

Standard HubSpot OAuth grant — required to identify which HubSpot account is connecting and to maintain a refreshable session. No data access on its own.

crm.objects.companies.read

Read company records (accounts) so Management OS can build the Account Plan, surface account context in the Weekly Brief's Business pillar, and answer Ask-Anything questions about specific customers.

crm.objects.contacts.read

Read contact records (buyers, champions, decision-makers) so Management OS can map stakeholder coverage on deals, identify champion-leaving signals, and surface multi-thread risk in the Brief.

crm.objects.deals.read

Read deal records so the Opportunity Scorer can grade pipeline against the 15-dimension / 75-criterion rubric (MEDDPICC + SPICED + Blue Sheet consolidated), surface deal-slip patterns, and lock the quarterly forecast.

sales-email-read

Read sales-email engagement (opens, clicks, replies) so the Brief surfaces buyer-intent signals at the deal and contact level. Email body content is NOT accessed via this scope — only engagement events.

Optional scopes (10)

These scopes are requested only when the customer's HubSpot tier has the corresponding feature enabled (e.g., crm.objects.custom.read is only relevant for HubSpot Operations Hub customers with custom objects). If the customer's tier does not include a feature, the corresponding optional scope is skipped without blocking the install.

crm.objects.users.read

Map HubSpot users to Management OS workspace members so coaching alerts and rep-effectiveness rankings are addressed to the correct person.

crm.objects.leads.read

Read lead records for top-of-funnel coverage in the Weekly Brief (where leads are tracked separately from deals).

crm.objects.appointments.read

Read scheduled appointments so Meeting Prep dossiers anchor on real upcoming meetings rather than calendar-only signals.

crm.objects.forecasts.read

Read forecast snapshots to track forecast accuracy drift over time and surface rep-side commitment changes in the Business pillar.

crm.objects.goals.read

Read sales goals and quotas to anchor rep-attainment, team-momentum, and comp-plan-attainment reads in the Weekly Brief.

crm.objects.products.read

Read product catalogs so deal line items are surfaced in the Account Plan and deal scorer (multi-product expansion signals).

crm.objects.quotes.read

Read sent quotes for stage-confidence signals in the deal scorer and the Forecast Call Prep brief.

crm.objects.projects.read

Read post-sale project status for renewal-risk signals in the Customer Success cluster of the Weekly Brief.

crm.objects.custom.read

Read custom CRM objects defined in the customer's HubSpot instance, so the Brief reflects their actual data model rather than only HubSpot's standard objects.

crm.objects.partner-clients.read

Read partner-client relationships for channel-partner attribution in the Account Plan and Brief.

4. Where your HubSpot data lives

Application database: Supabase Postgres (Management OS's production database, US East). Encrypted at rest (AES-256), encrypted in transit (TLS 1.3). Workspace-scoped row-level security (RLS) means one customer's data is never visible to another.

OAuth tokens: Stored in the same Supabase database under workspace-scoped RLS. Tokens are encrypted at rest and never returned to client browsers. Only the Management OS server-side runtime has access via service-role credentials.

Inference layer: Anthropic API (Claude models). CRM data required for a specific brief generation is passed to Anthropic; outputs are returned to Management OS and stored in our database. Anthropic does not train on customer data per their API terms.

Retention: We retain HubSpot-sourced data while your subscription is active. On disconnect we delete OAuth tokens immediately. On subscription cancellation, customer data is retained for 30 days for restoration, then permanently deleted. Data subject deletion requests are honored within 30 days per our Privacy Policy.

5. How to install Management OS for HubSpot

  1. Sign up at mgmt-os.ai and complete onboarding to your workspace
  2. Open Management OS → Settings → Integrations
  3. Find HubSpot in the integration directory and click Connect HubSpot
  4. You'll be redirected to HubSpot's authorization screen. Sign in with the HubSpot account you want Management OS to read from
  5. Review the requested scopes and click Connect app
  6. You'll return to Management OS with a confirmation that the integration is connected. The initial CRM sync starts immediately and typically completes within 2-5 minutes

If you administer HubSpot on behalf of an organization: Some HubSpot instances require admin pre-approval for new OAuth apps. If you encounter an approval prompt, your HubSpot admin can approve Management OS for organization-wide use.

6. How to use Management OS once connected

The Weekly Intelligence Brief is the primary surface. Three pillars synthesize your HubSpot data:

  • Develop Your Business — deal scoring (every open deal scored against the Opportunity OS rubric), forecast accuracy, account plans, champion-behavior alerts, renewal cascade
  • Develop Your Team — coaching priorities mapped to specific reps and deals, rep-effectiveness rankings, 1:1 prep, GROW conversation planners
  • Develop Yourself — leader focus, calendar audit, ninety-day competency focus, decision deadlines you're sitting on

Ask Anything (AMA) — a conversational surface where you can query your HubSpot data in plain English. Examples: "Which deals slipped this quarter?", "Show me the top 5 deals at risk with no champion activity in 14 days", "What's my coverage ratio against Q4 quota?"

7. How to disconnect from Management OS

  1. Open Management OS → Settings → Integrations
  2. Find HubSpot in the connected integrations list
  3. Click Disconnect → confirm

On disconnect we immediately delete the stored OAuth tokens and stop reading any new CRM data. Previously synthesized briefs remain in your Management OS workspace as historical records — they are not deleted automatically because they may contain decisions and context the leader still references.

To remove all historical briefs and data after disconnect, email privacy@mgmt-os.ai with your workspace identifier. We process deletion requests within 30 days.

8. How to revoke from HubSpot's side

  1. Sign in to HubSpot as an account administrator
  2. Open Settings → Integrations → Connected apps
  3. Find Management OS in the connected integrations list
  4. Click the integration → Uninstall or Revoke access

Revoking from HubSpot's side invalidates our tokens immediately. Our next API call returns 401 and we surface a re-connection prompt in Management OS Settings.

9. Security disclosures + contact

Security incident reporting: security@mgmt-os.ai
Privacy / data subject requests: privacy@mgmt-os.ai
Integration support: support@mgmt-os.ai

For general questions about Management OS, see our Support page or Manifesto.

Last updated: 2026-11-01. We update this page within 7 days of any change to scopes, data flows, or retention.