Skip to content

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Probo Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

Cal.com

Connect Cal.com as an access review source using OAuth or an API key so Probo can list your team's or organization's members.

View as Markdown

Probo reads your Cal.com team or organization members through the Cal.com API so you can review who has access. Connecting with OAuth is the recommended method and requires no token management. An API key is also available if you would rather not authorize an OAuth connection.

  • Probo organization administrator access
  • A Cal.com account that belongs to a team or an organization. A connected account with neither returns only itself (see Collected Fields)
Probo field Cal.com field Notes
Name user.name Falls back to the connected account’s own name when it belongs to no team or organization
Email user.email Falls back to the connected account’s own email when it belongs to no team or organization
Role membership.role Displayed as Owner, Admin, or Member; blank for a connected account with no team or organization
Admin membership.role Flagged as administrator when the role is OWNER or ADMIN
Status membership.accepted Active once the member accepts their invitation; a member active in at least one team counts as active
MFA Not supported
Last login Not supported
External ID userId Stable identifier used to track the account across reviews
Created at Not supported

If the connected account belongs to a Cal.com organization, Probo lists every member of that organization. Otherwise, Probo lists members across every team the connected account belongs to, combining a member who is on multiple teams into a single entry with every role they hold. A connected account with no team or organization returns only itself.

Section titled “Option A: Connect with Cal.com (recommended)”
  1. In Probo, go to Access Reviews > Sources > Add Source.
  2. Find Cal.com and click OAuth.
  3. Sign in to Cal.com and authorize Probo. Probo requests the PROFILE_READ, TEAM_PROFILE_READ, TEAM_MEMBERSHIP_READ, and ORG_MEMBERSHIP_READ scopes.
  1. In Cal.com, signed in as a team or organization admin, go to Settings > Developer > API keys, and create one.
  2. Name it (e.g. Probo Access Review) and copy the key. Cal.com shows it only once.
  3. In Probo, go to Access Reviews > Sources > Add Source, find Cal.com, and click API Key.
  4. Paste the key and click Connect.

Probo names the source “Cal.com” and pulls its members into your campaigns.

  • Key or token rejected, or no members appear. Confirm the API key or OAuth authorization belongs to a user who is a member of the team or organization you want to review.
  • Only the connected account appears. The connected Cal.com account has no team or organization, so Probo can only see that account. Add it to a team, or connect an account that already belongs to one.