Files & storage
Set up Guru
Connect Guru to make your team's knowledge cards searchable — every card the token's account can see becomes a document carrying its collection and verification state, so the team's verified answers are part of what the assistant knows. Read-only.
Before you start
- A Guru user token: in Guru open Settings → API access and generate a user token (an admin can also issue a collection-scoped token there). Copy it right away — it's shown once.
- The token works as a pair with the email of the account it belongs to, both from the SAME account. Cards are read as that account — it sees exactly the collections the account can see — and only reads are ever issued: nothing in Guru is changed.
- Documents → Guru: enter that account's email under Account email.
- Paste the token into User token.
- Choose access groups, Test, then Sync.
What comes in
- Each card becomes one document headed by its title, with a Collection line and a Verification line above the card's text, read as plain text with its formatting stripped, and dated by the card's last modification. A card with no text is left out.
- A verified (“Trusted”) card ranks above an unverified one, so the team's checked answer outranks a stale draft on the same topic.
Access
Each card follows the groups its collection is shared with, mirrored automatically from Guru's own collection permissions: every member of every group the collection is shared with becomes a viewer of its cards here, matched by email address and re-checked on every sync. A card marked private to specific people, rather than shared through its collection, falls back to the access groups chosen on the source — Guru's API doesn't say who those specific people are — and so does a collection shared with no group at all. Allow-only throughout. Switch How access works to “One list for everything” under Permissions to put everything this source brings in under the chosen access groups instead.
Cards are read as the token's account, so a collection that account can't see never appears. If the token can't read collection sharing at all (a non-admin token, typically), every card stays on the source's access groups and the sync summary says so — an admin's user token reads it fully. Test asks Guru for a single card and reports how many are reachable; it fails with a specific reason when Guru rejects the email-and-token pair. A sync stops at 3,000 cards, and collection sharing is read for up to 100 collections; the cut cards are missing from the listing, not deleted from Guru, so what already synced stays searchable.
Last updated 20 Sep 2026