Salesloft integration · Beta

What Management OS does with your Salesloft data.

How it connects: OAuth 2.0 through an application your admin registers in your Salesloft account, read-only scopes. Checked against the product on 5 November 2026.

1. What Management OS reads

  • People and accounts, and the user roster with team membership, so activity is attributed to the right seller.
  • Cadences and cadence memberships: who is being worked, by which cadence, and whether it is converting.
  • Emails: engagement counts and the subject line. Never the body.
  • Calls with disposition and sentiment, meetings, notes and tasks.

It reads only what the connected Salesloft user can see. Email bodies are never requested.

2. What it writes

Nothing. Every scope is a read scope and every request is a read. Management OS never writes to Salesloft.

3. The access it asks for, and why

Select exactly these scopes when you register the application in Salesloft. The connect page lists them too.

people:read, accounts:read

The people and accounts your team works.

cadences:read, cadence_memberships:read

Which cadence each person is in, and how far along.

emails:read

Email engagement and the subject line, to see what is landing. The body is not read.

calls:read, meetings:read

Calls with disposition and sentiment, and meetings, as evidence of progress.

notes:read, tasks:read

The context and follow-ups your team logged.

users:read, team:read

The roster, so activity is attributed to the right seller and leaders see their team.

4. How fresh the data is

  • A first sync is queued as soon as you connect; the Salesloft page shows counts as it runs. It goes back 90 days rather than through all history.
  • After that, Management OS reads Salesloft every 2 hours, picking up only what changed.
  • Salesloft gives your team one shared API budget per minute. Management OS stops a run while plenty of that budget is left for your other tools and continues on the next cycle.

5. Where it shows up in Management OS

  • Your Desk and morning brief: cadences, replies and calls joined to your pipeline. Each seller sees their own book; leaders see their team.
  • Ask Anything: questions about cadences, replies and calls, answered from the synced records.

6. Where your Salesloft data lives

Your credential. The client secret and every user's tokens are sealed with application-layer encryption before they are stored, and are never shown back in your browser. Salesloft rotates the refresh token on every refresh, so Management OS stores the new pair before doing anything else, and only one process refreshes a given connection at a time. If Salesloft refuses the grant, the page shows Reconnect.

Hosting. Runs in the United States on Vercel and Supabase.

AI processing. The data a brief or an answer needs is sent to Anthropic or OpenAI, on API terms that prohibit training. Each keeps prompts up to 30 days for abuse monitoring, with narrow exceptions listed on Sub-processors. We do not use Customer Data, prompts, or AI Output to train, fine-tune, or improve any AI model, including our own.

If you leave. Revoke access at any time, and export or delete your data on request. Active data is deleted within 30 days of termination; encrypted backups roll off within 90 days. See the Privacy Policy and the Data Processing Addendum.

7. How to connect Salesloft

Before you start.

  • Salesloft takes a few more steps than most connections, by design: your admin registers Management OS as an application in your own Salesloft account, so the connection stays under your control and does not wait on a vendor review.
  • A Management OS workspace owner or admin to register the Salesloft application once. Members see who to ask.
  • A Salesloft user who can create OAuth applications in Salesloft.
  1. Open Management OS, then Settings, then Integrations. Find Salesloft and choose Connect. The page shows the Redirect URI and the scopes to select.
  2. In Salesloft, open Account, then Your Applications, then OAuth Applications, and create a new application named Management OS. Paste the Redirect URI, select the scopes listed and save.
  3. Back in Management OS, an owner or admin enters the Client ID and Client secret and saves them.
  4. Each seller then chooses Connect, signs in to Salesloft and approves read-only access for their own user. The first sync starts.

8. How to disconnect

On the Salesloft page in Settings, choose Disconnect. Management OS deletes your stored tokens and stops reading for your user. The disconnect is recorded in your workspace's audit log.

Salesloft has no call that lets Management OS revoke the grant, so the grant lapses unused. Remove the application from your Salesloft account to end it at once.

An owner or admin can also remove the workspace's application from the same page. Records already synced stay in your workspace until you ask for them to be deleted at privacy@mgmt-os.ai.

9. How to revoke access from Salesloft

In Salesloft, remove the Management OS application from your account, or delete the OAuth application your admin registered. Salesloft then refuses the tokens and the page in Management OS shows Reconnect.

10. If something goes wrong

The page says Salesloft did not complete the connection.
Salesloft returned an error during sign-in, shown in brackets. The most common causes are a Redirect URI that does not match the one on the page exactly, or scopes missing from the application. Fix the application in Salesloft and connect again.
Some data is missing after the first sync.
If a scope was not selected on the application, that part of the sync is skipped and the rest continues. Add the scope in Salesloft, then disconnect and connect again.
Members see Not set up yet.
A workspace owner or admin needs to register the Salesloft application and save its Client ID and secret first.

11. Contact

Help connecting: support@mgmt-os.ai
Privacy and data requests: privacy@mgmt-os.ai
Security reports: security@mgmt-os.ai

Every other guide is on the Help page, and every connection is listed on Integrations.