What Management OS does with your Zoho CRM data.

Management OS reads CRM data from your Zoho CRM org — specifically: all standard CRM modules (Accounts, Contacts, Deals, Leads, Tasks, Events, Calls) and any custom modules you have defined, plus CRM settings metadata (module layouts, picklists, custom fields, user list, role hierarchy). We do not access Zoho Mail, Zoho Books, Zoho Desk, Zoho Projects, Zoho Campaigns, Zoho Cliq, or any other Zoho One product. Read access is gated by the connecting user's CRM profile and data-sharing rules.

Multi-datacenter: Zoho returns an api_domain at token exchange (e.g. https://www.zohoapis.com for US, .eu for EU, .in for India). All REST calls target only that data center — we never read across regions.

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.

We do not write to your Zoho CRM. Management OS is a read-only consumer of your Zoho data. We do not create, modify, or delete any Zoho CRM records — no Accounts, no Contacts, no Deals, no Leads, no Tasks, no Events, no Notes, no custom modules, no workflow triggers.

We requested the .READ variant of every scope (never .ALL or .WRITE), enforced at the Zoho authorization server.

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 Zoho CRM org.

Every scope below maps to a specific feature. Both scopes are .READ-only; we did not request any write or admin scopes.

Required scopes (2)

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

Module-level granularity: Zoho's ZohoCRM.modules.READ scope covers all modules in a single grant. The practical limit on what Management OS can read is the connecting user's Zoho profile and data-sharing rules — not the OAuth scope set. If you want to further limit what Management OS can see, create a dedicated Zoho user for the integration with a profile scoped to the exact modules and fields you want exposed.

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. Access tokens, refresh tokens, and the per-datacenter api_domain 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 Zoho-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.

Cross-region note: Even if your Zoho data lives in the EU or another non-US data center, Management OS reads and persists summaries into Supabase US East. If your compliance posture requires data to remain in-region, please reach out to privacy@mgmt-os.ai before connecting.

1. Sign up at mgmt-os.ai and complete onboarding to your workspace
2. Open Management OS → Settings → Integrations
3. Find Zoho CRM in the integration directory and click Connect Zoho CRM
4. You'll be redirected to Zoho's authorization screen on your data center (accounts.zoho.com, accounts.zoho.eu, accounts.zoho.in, and so on). Sign in with the Zoho user you want Management OS to read as
5. Review the requested scopes (ZohoCRM.modules.READ, ZohoCRM.settings.READ) and click Accept
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 5-15 minutes depending on org size

If you administer Zoho CRM on behalf of an organization: Some Zoho orgs require admin approval before users can authorize third-party apps. If you encounter an approval prompt, your Zoho admin can approve Management OS via the Zoho CRM Admin Panel.

The Weekly Intelligence Brief is the primary surface. Three pillars synthesize your Zoho CRM 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 Zoho data in plain English. Examples: "Which deals slipped from this quarter to next?", "Show me the top 5 deals at risk with no activity in 14 days", "What's my coverage ratio against Q4 quota by rep?"

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

On disconnect we immediately delete the stored OAuth tokens (access, refresh, and api_domain) 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.

1. Sign in to Zoho Accounts at accounts.zoho.com (or your data-center equivalent)
2. Open Security → Active Sessions and Connected Apps
3. Switch to the Connected Apps tab
4. Find Management OS in the list and click Remove

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

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.