Skip to content

Connecting your sources

For administrators

Telha answers from your company's own systems. Connecting a source lets Telha read it, keep it in sync, and turn it into memory you can ask questions about, while respecting exactly who is allowed to see what.

For administrators

Connecting a source is a one-time setup done by an administrator, working with your IT team and your Telha administrator. Everyday users never do this; they just get better answers once sources are connected.

What connecting a source gives you

  • Answers grounded in your systems, not a separate copy you have to maintain.
  • Provenance: every fact Telha learns links back to the exact item it came from, so you can open it in the original system in one click.
  • It stays current: connectors sync on a schedule, pick up changes, and propagate deletions so Telha does not answer from something that was removed.

The permission promise

This is the most important thing to understand before you connect anything:

You never see more in Telha than you can see at the source

Telha's own access rules (mapped from your directory) are the single gate on what anyone sees. Where a source has its own permissions, Telha can only use them to narrow access further, never to widen it. If you cannot see a document in SharePoint, you cannot see it through Telha either. See Trust & privacy.

Connect identity first

Start with the Entra ID connector. It maps your organisation's people and groups (and who reports to whom) so that Telha knows who everyone is. Everything else depends on it: it is how permissions are enforced, how Telha decides who to ask when it needs a clarification, and how every action is tied to a real, verified person.

Register Read permission Telha needs
An app in Entra ID (Azure) User.Read.All, Group.Read.All, GroupMember.Read.All

The source connectors

Once identity is in place, connect the systems that hold your content. Each one is read-only, syncs on a schedule, and you choose exactly what it covers.

Source What Telha brings in You register You choose
SharePoint / OneDrive Documents (PDF, Word, PowerPoint, spreadsheets), with author and owner An Entra app with Sites.Read.All, Files.Read.All Which sites to include
Exchange / Outlook Email and attachments An Entra app with Mail.Read Which mailboxes to include
Slack Channel conversations (threads become documents) A Slack app with read scopes Which channels to include
Salesforce Records for the objects you choose (accounts, opportunities, cases, and so on) A connected app (read-only integration user) Which objects to include

Nothing syncs until you say so

Every connector starts empty. It only reads the sites, mailboxes, channels, or objects you explicitly add to its list, so you can start small and expand.

What Telha keeps in sync

  • Changes are picked up automatically on each sync (every 30 to 60 minutes by default).
  • Deletions in SharePoint, Exchange, and Salesforce are reflected in Telha, so a removed document stops appearing in answers. (Slack conversations are not deleted this way, by design.)
  • Who wrote and owns things rides along, so when Telha needs to confirm a detail it can ask the right person, and every answer can deep-link back to the original.

Good to know

  • Connectors are read-only. Telha never writes back into your systems.
  • A connector can only ever touch its own data. The SharePoint connection can never affect Slack-sourced or manually added information, and vice versa.
  • Permissions can lag between syncs. Because Telha's own access rules are the real gate, this never exposes anything; a source's permission list is only ever used to hide more, never to reveal.