Skip to main content
Connect only the sources you are authorized to use. Each source adds a different kind of relationship context.
Last verified against current extension, dashboard, and API source on August 11, 2026.

​
LinkedIn

The Introd-provided Chrome extension currently supports:
  • detecting whether LinkedIn is signed in in the same Chrome profile
  • importing visible first-degree connection identities and sync status
  • continuously deriving visible identity and relationship fields while permitted LinkedIn pages change, when the default capture settings are on
  • processing identity containers on profiles, feeds, comments, messaging surfaces, hover cards, organization people pages, events, discovery results, and lists
  • automatically resuming an incomplete full-network import in an inactive connections tab
  • showing available warm-path context beside supported identities
The extension does not ask for your LinkedIn password or send connection requests, messages, or introductions. LinkedIn visibility, page rendering, session state, and rate limits can make a sync partial. Review the popup status before treating the imported count as complete. The documented capture data includes profile identity, URL, headline or role, current and past work, education, company, location, image, connection degree, and mutual-connection context when those fields are visible. Profile-view signals can be stored locally and uploaded on a schedule; authenticated captures can be submitted for enrichment. The payload does not define a dedicated message-body field. Current relationship parsing can nevertheless inspect surrounding rendered text, including on LinkedIn messaging surfaces, and Introd has not completed a runtime attestation proving message-page text cannot leave the browser. Pause Sync stops full-network import and its automatic background resume; it does not stop contextual browsing capture or current-page diagnostics. The settings toggles skip new profile-view signals and enrichment but do not stop diagnostics, full-network recovery, or upload of signals already queued while authenticated. Disabling the extension in Chrome is the reliable way to stop its code from running on LinkedIn pages. See LinkedIn Integration for the complete control matrix.

​
Google Workspace

The current Google sync requests access to:
  • Gmail metadata, including available From, To, Cc, Bcc, Date, and Subject headers
  • read-only Calendar event metadata
  • read-only Contacts data
  • basic account identity needed to connect the correct provider account
The current sync does not import Gmail message bodies, meeting contents, or private notes.

​
Microsoft 365

The current Microsoft sync requests access to:
  • basic Outlook mail metadata exposed through Mail.ReadBasic
  • read-only Outlook Calendar metadata
  • basic account identity needed to connect the correct provider account
The current sync is configured for metadata-only mail processing. It does not import Outlook message bodies, meeting contents, or private notes.

​
How Introd uses this data

Authorized provider data can contribute to:
  • searchable people and company records
  • available connector and path context
  • relationship evidence counts and sync status
  • TrustRank, confidence, or relationship-strength signals shown by the product
Those signals rank available evidence. They are not guarantees that a relationship is current, that a connector will agree, or that an introduction will succeed.

​
Disconnect behavior

For Google Workspace and Microsoft 365:
  1. Open Integrations.
  2. Open the connected provider card.
  3. Choose Disconnect and confirm.
Expected result: Introd clears its stored connection tokens and stops future sync jobs. Previously imported Introd records remain. Revoking provider-side consent and deleting imported data are separate actions. See Deletion and Privacy Requests.

​
Sync failures

For the exact provider scopes, see OAuth Permissions.
Last modified on August 17, 2026