Skip to content

Fathom Integration

The Fathom integration connects your Fencer organization to your Fathom (AI meeting recorder) account, syncing team members into Fencer’s identity management module. This gives you visibility into who has access to your Fathom account alongside identities from your other connected SaaS tools.

  • An active Fencer subscription.
  • Admin role in your Fencer organization.
  • Owner or admin permissions on your Fathom team.

Fencer connects to Fathom using OAuth 2.0. When you authorize the connection, Fencer receives an access token scoped for read access to your team’s member list. Fencer uses this token to list your Fathom team members and syncs each one as a vendor identity, using their email as the identifier. Identity sync runs automatically once the connection is established.

Fathom is an identity-sync integration only — connecting it does not add any scanning or vulnerability checks.

  1. Navigate to Settings > Integrations in your organization.
  2. Find the Fathom integration and click Connect.
  3. You will be redirected to Fathom’s authorization page. Sign in if prompted.
  4. Authorize Fencer’s access to your team’s member list.
  5. You are redirected back to Fencer. The integration is now active, and identity sync begins automatically.

Fencer syncs your Fathom team members, using each member’s email address and name. Synced members appear in the Identity Management module as Fathom vendor identities.

  1. Navigate to Settings > Integrations.
  2. Find the active Fathom connection and click Delete.
  3. Fencer clears the stored OAuth tokens and removes the connection.

Syncing a Fathom team for identity visibility:

  1. Your organization uses Fathom to record and transcribe meetings.
  2. Navigate to Settings > Integrations and connect the Fathom integration.
  3. After authorization, Fencer syncs your Fathom team members.
  4. Open Identity Management to see Fathom identities alongside identities from other connected providers.
  • “Failed to connect Fathom” error — This typically means the OAuth token exchange failed. Try reconnecting the integration.
  • Connection shows as unhealthy — The access token may have expired. Disconnect and reconnect to obtain a fresh token.
  • Missing users in identity sync — Fencer can only see the team members visible to the authorizing account. Confirm you authorized with an owner or admin account on the correct team.