Guru

The Guru integration makes your firm’s verified knowledge available in client work. Ask what the approved pricing review methodology says about sample size, which card covers the data request checklist, or whether a card is still verified, and Hebno answers from Guru with each card and its verification status cited. When you want a result kept in Guru, Hebno drafts the card and creates it only after you confirm.

​

At a glance

​

Before you start

You need:

• A Guru account with access to the collections you want to use. Hebno reads only the collections and cards your Guru groups allow.
• Author or higher permission on a collection where you want to create drafts.
• An allowed integration. An owner or admin sets Guru to Allow under Admin → Connectors → Catalogue.
• A Guru user token. In Guru, open Apps & Integrations → API Access, select Generate User Token and copy it.

Hebno calls the Guru API with your email address and user token, so every request runs with your own Guru permissions:

​

Connect Guru

Hebno stores the token encrypted at rest. To revoke it, delete it in Guru under API Access, or select Disconnect in Hebno. Admins can revoke any member’s connection from Admin → Connectors → Connections.

​

What Hebno reads

The collections your organisation selects are stored in the knowledge index and searched by meaning, with Guru permissions checked at search and again at read. Opening a specific card reads it as it is now, with your token. Only the excerpts a reply used are stored with the conversation as its sources. Each source shows the card’s verification state. When a card is marked Needs verification, the reply says so and names the verifier, so you can check with them before you rely on it.

​

What Hebno writes

Every draft appears first as a confirmation card. You can change any field before you select Confirm. The draft is saved under your Guru account, in My Drafts. You or another author reviews it in Guru, sets the verifier and interval, and publishes it to the collection. Hebno never publishes, verifies, edits, archives or deletes cards, and never changes collection permissions.

​

Link a project to a collection

Linking marks which Guru collections or folders belong to an engagement, so you can ask “what is our method?” without naming the collection.

1. Open the project and select Brain.
2. Under Linked sources, select Link source, then Guru.
3. Search by collection or folder name and select Link.

In chats tagged to the project, Hebno searches the linked collections first, and draft cards default to them. Each person still reads cards with their own Guru access. See Linked records.

​

Use Guru in chat

• Attach: open the + menu, choose Sources → Guru, and pick a card, a folder or a collection. Or type / and choose Guru.
• Ask: name the method, policy or collection in your request. For example:

  What does our pricing review method say about choosing test and control stores? Cite only verified cards.

  Build a kickoff agenda for Contoso Retail from the engagement kickoff and data request cards.

  Save this interview guide as a draft card in the Pricing reviews folder, tagged retail.

• Research runs show a Reviewing Guru step, with a chip for each card Hebno read and its verification state.
• Agents can read Guru on a schedule. Drafts an agent proposes appear in agent approvals for review.

​

Troubleshooting

​

Related

• How integrations work
• Permissions and access
• Confluence
• Notion
• Workspace library