What Management OS does with your Lightfield data.

Management OS reads CRM data from your Lightfield workspace — specifically: accounts, contacts, deals, activities, and users. We do not access Lightfield agent configurations, agent-source-code, billing data, or any workspace data outside the read surface listed above.

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. Lightfield's agent-native model is interesting here — we read both human-logged and agent-logged activities, which means the Brief sees the full coverage picture even when agents are doing the work.

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

We only invoke GET endpoints on Lightfield's API. We never invoke POST, PUT, PATCH, or DELETE. If you create your API key with read-only scopes (recommended), the key is also incapable of writing — defense in depth.

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 Lightfield workspace.

Lightfield uses per-user API keys (no OAuth flow), so the permission set is selected by you when you create the key in the Lightfield admin dashboard. The recommended read-only scope set below covers the full Management OS feature surface; selecting fewer scopes will degrade specific features as noted.

Recommended read-only scopes (5)

When you create the API key, select these scopes. The required minimum is accounts:read — without it, no useful synthesis is possible. Each additional scope unlocks a specific feature surface.

Do not select write scopes. Management OS never writes to Lightfield. Selecting write scopes (e.g. accounts:write) would over-grant your API key relative to what the integration needs.

API key format + headers: Lightfield keys are formatted sk_lf_0_... and passed as Authorization: Bearer {key} with a required Lightfield-Version: 2026-03-01 header. Management OS pins to a specific API version so upstream schema changes do not silently break the Brief.

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.

API key storage: Stored in the same Supabase database under workspace-scoped RLS. Keys are encrypted at rest and never returned to client browsers. Only the Management OS server-side runtime has access via service-role credentials. We never log or display the key after the initial save.

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 Lightfield-sourced data while your subscription is active. On disconnect we delete the API key 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.

1. Sign in to Lightfield as an admin and open Settings → API Keys (crm.lightfield.app/crm/settings/api-keys)
2. Click Create new key. Name it management-os so you can identify it later
3. Select the recommended read-only scopes: accounts:read, contacts:read, deals:read, activities:read, users:read
4. Click Create and copy the key (format sk_lf_0_...). Lightfield only shows it once
5. Sign up at mgmt-os.ai and complete onboarding to your workspace
6. Open Management OS → Settings → Integrations → find Lightfield → click Connect Lightfield
7. Paste the API key into the form and click Save. Management OS validates the key against Lightfield's API immediately; the initial CRM sync starts on success and typically completes within 2-5 minutes

The Weekly Intelligence Brief is the primary surface. Three pillars synthesize your Lightfield 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 Lightfield data in plain English. Examples: "Which deals slipped this quarter?", "Show me deals where the agent has logged five activities and the rep has logged zero", "What's my coverage ratio against Q4 quota?"

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

On disconnect we immediately delete the stored API key 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.

Note: Deleting the key from Management OS does not invalidate it on Lightfield's side. For full revocation, also revoke the key in the Lightfield admin dashboard (see next section).

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 Lightfield as an admin
2. Open Settings → API Keys (crm.lightfield.app/crm/settings/api-keys)
3. Find the key named management-os (or whatever you named it at creation time)
4. Click Revoke

Revoking the key invalidates it immediately on Lightfield's side. Our next API call returns 401 and we surface a re-connection prompt in Management OS Settings.

Admin-only: API key revocation in Lightfield is restricted to workspace admins.

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.