Skip to content

Personal connectors

Personal connectors let Know reach your own personal and record-level data live, under your own credentials, without ever writing it into the shared knowledge graph. They are set up per user — what you connect is yours alone.

Why they're per user

The organization knowledge graph is shared, so anything brought into it is readable by everyone via Know. Personal, record-level, and sensitive data must therefore stay out of the graph. Personal connectors solve this:

  • Nothing is brought into the graph. Liddr reaches the source only when one of your questions needs it.
  • It runs as you. Each connector uses your own credentials, so you only ever see what you're already allowed to see.
  • It's live. Results reflect the source at the moment you ask, not a stored snapshot.

This is why sources like Slack, Box, Dropbox, Gmail, and CRM or support systems are personal connectors rather than shared ones. For the full reasoning, see the access principle.

Connect a personal connector

  1. Open Settings → Connections and choose Add connector.
  2. Pick a personal connector from the catalog.
  3. Sign in or authorize it. Most connect with a single click; a few ask you to paste a token, and open sources need no sign-in at all.
  4. Click Test to confirm it works.

Available connectors

The catalog includes these personal connectors:

ConnectorNotes
SlackYour channels and messages, live.
BoxYour Box content.
DropboxYour files.
ZoomYour meetings, recordings, and AI Companion.
DocuSignYour envelopes and agreements.
NotionOne-click authorize.
LinearOne-click authorize.
SentryOne-click authorize.
GitHubAuthorize, or paste a personal access token.
StripeAuthorize, or paste a restricted API key.
Google CalendarYour calendar and events.
GmailYour mailbox.
Google DriveYour files.
Hugging FacePaste an access token.
Context7 (library docs)Public — no sign-in required.

TIP

Notion, Linear, Sentry, and GitHub appear both as shared connectors and as personal connectors. The shared connector brings org-wide content into the graph for everyone; the personal connector gives you live, personal access to the same system. They are complementary, not redundant.

How Know uses your connectors

When you ask a question that needs personal or record-level data — say, your latest emails or a file in your Drive — Know reaches the right connector, fetches the data under your credentials, and uses it to answer. Because the data came through a personal connector, the answer is flagged as having used one, keeping personally-fetched results separate from the shared graph.

Liddr — grounded in your reality, linked to the evidence.