Guru integration

What Management OS does with your Guru knowledge.

How it connects: a Guru User API token and the email of the Guru user who created it. Checked against the product on 5 November 2026.

1. What Management OS reads

  • Team-shared cards: title, content, collection, folders, tags and verification state.
  • Your collections, so you can choose which ones to sync. Leave them all unticked to sync every team-shared collection.

Private cards are never read. Archived cards are not listed.

2. What it writes

Guru content is never edited. The only thing Management OS creates in Guru is a webhook subscription, and only if you turn on real-time updates. It is deleted when you turn real-time off or disconnect.

3. The access it asks for, and why

Guru User API tokens act as the Guru user who created them. Management OS sees what that user can see, minus private cards.

Guru user email

The Guru user who created the token. Guru's API signs in with the email and token together.

Guru API token

A User token from Guru's Settings, API Access. Used to list cards and collections, read each card, and manage the real-time webhook if you turn it on.

4. How fresh the data is

  • A first sync is queued as soon as you connect. The Guru page shows counts as it runs.
  • After that, cards refresh every 2 hours. Only cards that changed are processed again.
  • Real-time updates, if you turn them on: card creations, edits, verifications, deletions and restores arrive within seconds.
  • Sync now on the Guru page queues a refresh at any time.

5. Where it shows up in Management OS

  • Ask Anything: answers search your team's Guru knowledge, cite the card they used, and can say when that card needs verification.

6. Where your Guru data lives

Your credential. The token is sealed with application-layer encryption before it is stored, and is never shown back in your browser or written to logs. Changing your collection choice asks for the token again for the same reason. If Guru rejects the token, the Guru page says so and asks you to create a new User token and connect again.

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 Guru

Before you start.

  • A Guru user who can create a User token, with access to the collections you want in Management OS.
  1. In Guru, open Settings, then API Access, and generate a User token.
  2. Open Management OS, then Settings, then Integrations. Find Guru and choose Connect.
  3. Enter the Guru user email and the Guru API token, and connect. Management OS checks them with Guru before saving.
  4. The first sync starts. Optionally, pick the collections that matter to revenue, and turn on real-time updates.

8. How to disconnect

In Management OS, open Settings, then Integrations, then Guru, and choose Disconnect.

Management OS deletes the real-time webhook in Guru if there is one, removes the cards this connection brought in from your workspace's knowledge, and deletes the stored token. The disconnect is recorded in your workspace's audit log.

9. How to revoke access from Guru

In Guru, revoke the User token in Settings, then API Access. If real-time updates were on, also check that the Management OS webhook is gone.

10. If something goes wrong

The Guru page says Guru rejected the token.
Create a new User token in Guru, disconnect, and connect again.
A card I expect is missing.
Private cards are never read, and only the collections you picked are synced. Check the card's sharing and your collection selection.

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.