π Best Practices: Deciding how to connect your information to Guru
This guide helps you decide how to connect and manage your teamβs content in Guru.
Comparing Content Strategies
Strategy | Best for... | Requires verification in Guru? | Editable in Guru? | Stored in Guru? | Updates in Guru after the original document is updated |
---|---|---|---|---|---|
Migrate it into Guru | Dynamic, business-critical content that needs regular verification and governance | β Yes | β Yes | β Yes | β No |
Connect a Source | Static, compliance-bound, or archival content that is regularly verified in the original source | β No | β No | β No | β Yes |
Connect a Knowledge Sync | Content from Zendesk Guide, Salesforce Knowledge, Confluence Pages that can be referenced in Guru Cards | β Partial | β No | β Yes (Card) | β Yes |
Embed it in a Guru Card or Page | External content to be referenced in a Guru Card or Page | β Partial | β No | β Yes (Card) | β Yes |
Migrating content into Guru Collections
Best for:
- Prioritizing Guru instead of other knowledge repositories
- Content that changes frequently
- Knowledge where accuracy and freshness are essential
Examples:
- Support SOPs and FAQs
- Product specs and live service guides
- Pricing rules, legal disclaimers, API access info
- Onboarding flows and training content
- CRM glossaries and sales enablement materials
Why import:
- Enables verification workflows
- Assigns ownership and review intervals
- Keeps critical info centralized and trusted
See: Migrating knowledge into Guru
Connecting external Sources
Best for:
- Static or historical reference material
- Data maintained elsewhere for compliance
- Contextual info
- Generating AI Answers without needing to give every user a seat in the Source
Examples:
- Support tickets and chat logs (e.g., Zendesk, Intercom)
- Salesforce fields and customer attributes
- Regulatory docs and code repositories
- Call transcripts, webinar recordings
Why connect:
- Avoids duplication and manual upkeep
- Preserves native access and compliance
- Lets Guru surface info directly from the Source
Connecting a Knowledge Sync
Best for:
- Reflecting content from Zendesk Guide, Salesforce Knowledge, or Confluence Pages in Guru Cards
- Accessing full content from Zendesk Guide, Salesforce Knowledge, or Confluence Pages without needing to pivot out of Guru
- Requiring verification of Cards, which could help prompt the SME to edit the content in Zendesk Guide, Salesforce Knowledge, or Confluence Pages
See: Creating a Knowledge Sync
Embedding content in Guru Cards
Best for:
- Quick-referencing basic content as it's represented in another place
- Adding a short blurb about the embedded or uploaded document so your team can get the basic knowledge they need, and also peruse the full document if they want to dive deeper.
See: Embedding content into Guru Cards
Examples:
- Spreadsheets and tables from Google Sheets, Smartsheet, etc.
- Videos from Loom, Wistia, Youtube, etc.
- Design files from Figma, Sketch, InVision, etc.
- Google Maps, Google Calendars, etc.
- Diagrams and Charts from Lucidchart, Miro, Google Draw, etc.
Why embed:
- Avoids duplication and manual upkeep
- Preserves native access and compliance
- Lets a Guru Card display content from its original home for quick reference
Want a closer look at some key Guru features and best practices?Check out our events page for demos, workshops, new release roundups, Getting Started bootcamp, guest panelists and more! For upcoming live events and a series of past recordings: Click here to register
Updated 17 days ago