SCIM Provisioning

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/calcom/cal.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

• Automated User Provisioning: Automatically create users when added to IdP
• Deprovisioning: Remove access when users leave the organization
• Attribute Sync: Keep user profiles synchronized with IdP
• Group Management: Map IdP groups to Cal.com teams
• Real-time Updates: Changes in IdP reflect immediately in Cal.com

​

Prerequisites

• Cal.com Enterprise license
• Organizations feature enabled
• SSO/SAML configured (see SAML Setup)
• Identity Provider supporting SCIM 2.0
• SAML database configured

​

Supported Identity Providers

​

Setup Guide

​

1. Prerequisites Configuration

# Required: SAML database (shared with SCIM)
SAML_DATABASE_URL=postgresql://postgres:@localhost:5450/cal-saml

# Required: Encryption key
CALENDSO_ENCRYPTION_KEY=your_encryption_key

# Required: SAML admins
SAML_ADMINS=admin@company.com

# Optional: Enable SCIM request logging for specific directories
DIRECTORY_IDS_TO_LOG=dir_123,dir_456

​

2. SCIM Endpoint Configuration

Base URL: https://your-domain.com/api/scim/v2.0

• /Users - User management
• /Groups - Group/team management
• /ServiceProviderConfig - SCIM configuration
• /ResourceTypes - Supported resource types
• /Schemas - SCIM schema definitions

​

3. Generate SCIM Token

1. Log in to Cal.com as a SAML admin
2. Navigate to Settings → Security → Directory Sync
3. Select your organization
4. Click “Create Directory”
5. Choose your identity provider
6. Copy the generated SCIM token and endpoint URL

​

4. Configure Identity Provider

​

Azure AD / Entra ID

1. Navigate to your Enterprise Application
2. Select Provisioning → Automatic
3. Configure:
   • Tenant URL: https://your-domain.com/api/scim/v2.0
   • Secret Token: [SCIM token from step 3]
4. Click “Test Connection”
5. Configure Attribute Mappings:
   userPrincipalName → userName
   mail              → emails[type eq "work"].value
   givenName         → name.givenName
   surname           → name.familyName
   displayName       → displayName
   
6. Set Provisioning Status to “On”
7. Save and perform initial sync

​

Okta

1. Navigate to Applications → Your SAML App
2. Go to Provisioning tab → Configure API Integration
3. Enable API integration
4. Configure:
   • Base URL: https://your-domain.com/api/scim/v2.0
   • API Token: [SCIM token from step 3]
5. Test API Credentials
6. Enable provisioning features:
   • ✅ Create Users
   • ✅ Update User Attributes
   • ✅ Deactivate Users
   • ✅ Sync Password (optional)
7. Configure Attribute Mappings:
   userName      → email
   email         → email
   givenName     → firstName
   familyName    → lastName
   
8. Save and assign users to application

​

JumpCloud

1. Navigate to SSO Applications → Your Cal.com App
2. Enable Identity Management
3. Configure:
   • SCIM Version: 2.0
   • Base URL: https://your-domain.com/api/scim/v2.0
   • Token Key: Authorization
   • Token Value: Bearer [SCIM token]
4. Configure Attribute Mappings:
   email         → email
   firstname     → name.givenName
   lastname      → name.familyName
   username      → userName
   
5. Activate provisioning

​

OneLogin

1. Navigate to Applications → Your SAML App
2. Go to Provisioning tab
3. Enable Provisioning
4. Configure:
   • SCIM Base URL: https://your-domain.com/api/scim/v2.0
   • SCIM Bearer Token: [SCIM token from step 3]
5. Enable:
   • ✅ Enable provisioning
   • ✅ Create user
   • ✅ Delete user
   • ✅ Update user
6. Configure Field Mappings
7. Save and run provisioning

​

User Lifecycle Management

​

User Creation

// SCIM creates user with attributes
const event = {
  event: "user.created",
  data: {
    email: "user@company.com",
    firstName: "John",
    lastName: "Doe",
    active: true,
  },
};

// Cal.com processes:
1. Check if user exists in database
2. If not, create new user with SAML identity provider
3. Connect user to organization based on email domain
4. Send invitation email
5. Sync custom attributes from SCIM payload

​

User Updates

// SCIM sends update event
const event = {
  event: "user.updated",
  data: {
    email: "user@company.com",
    firstName: "Jane", // Changed
    active: true,
  },
};

// Cal.com processes:
1. Find user by email
2. Update user attributes
3. Sync custom attributes to user profile
4. If user is member, sync attributes to organization

​

User Deactivation

// SCIM sends deactivation event
const event = {
  event: "user.updated",
  data: {
    email: "user@company.com",
    active: false, // Deactivated
  },
};

// Cal.com processes:
1. Find user by email
2. Remove user from organization
3. Revoke organization membership
4. Cancel pending workflows and bookings (optional)
5. User retains account but loses org access

​

User Deletion

// SCIM sends deletion event
const event = {
  event: "user.deleted",
  data: {
    email: "user@company.com",
  },
};

// Cal.com processes:
1. Find user by email
2. Remove from organization
3. User account remains (can be deleted manually)

​

Custom Attribute Synchronization

​

SCIM Schema

Core Schema URN: urn:ietf:params:scim:schemas:core:2.0:User

​

Custom Attributes

// Example SCIM payload with custom attributes
{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:User",
    "custom:enterprise"
  ],
  "userName": "user@company.com",
  "custom:enterprise": {
    "department": "Engineering",
    "employeeNumber": "12345",
    "costCenter": "R&D"
  }
}

// Cal.com extracts and stores:
const customAttributes = {
  department: "Engineering",
  employeeNumber: "12345",
  costCenter: "R&D"
};

​

Attribute Assignment

await assignValueToUserInOrgBulk({
  orgId: organization.id,
  userId: user.id,
  attributeLabelToValueMap: customAttributes,
  updater: {
    dsyncId: directoryId, // Tracks SCIM as source
  },
});

​

Attribute Pools

1. SCIM Pool: Attributes managed by SCIM directory
2. Cal.com User Pool: Attributes managed by Cal.com users

• SCIM updates only affect SCIM pool attributes
• Cal.com users can override SCIM attributes (moves to User Pool)
• Multiple SCIM directories can coexist
• Deleting SCIM directory only removes its pool attributes

​

Group Management

​

Group Events

// Group creation
const event = {
  event: "group.created",
  data: {
    name: "Engineering",
    members: [
      { value: "user1@company.com" },
      { value: "user2@company.com" },
    ],
  },
};

// Cal.com processes:
1. Create or map to existing team
2. Add group members to team
3. Set appropriate permissions

​

Team Mapping

• Group display name → Team name
• Group members → Team members
• Nested groups supported (if IdP supports)

​

Monitoring and Debugging

​

Enable SCIM Logging

# Comma-separated list of directory IDs to log
DIRECTORY_IDS_TO_LOG=dir_abc123,dir_xyz789

​

Check Provisioning Status

1. Log in as SAML admin
2. Navigate to Settings → Security → Directory Sync
3. View sync status and logs:
   • Last sync time
   • Users provisioned
   • Errors and warnings
   • Pending operations

​

Common Log Entries

[SCIM] User created: user@company.com
[SCIM] User updated: user@company.com
[SCIM] User deactivated: user@company.com
[SCIM] Custom attributes synced: department, role
[SCIM] Group created: Engineering

​

Troubleshooting

​

SCIM Connection Test Fails

1. Verify SCIM endpoint URL is correct
2. Check SCIM token is valid and not expired
3. Ensure SAML_DATABASE_URL is configured
4. Verify network connectivity to Cal.com
5. Check firewall rules allow IdP to reach endpoint

​

Users Not Provisioning

1. Verify users are assigned to the application in IdP
2. Check attribute mappings are correct
3. Ensure email format is valid
4. Verify organization auto-linking is configured
5. Check user doesn’t already belong to another organization

​

Custom Attributes Not Syncing

1. Verify custom schema is included in SCIM payload
2. Check attribute names match expected format
3. Ensure custom attributes are mapped in IdP
4. Review SCIM request logs with DIRECTORY_IDS_TO_LOG

​

Group Mapping Issues

1. Verify groups are assigned to application in IdP
2. Check group provisioning is enabled
3. Ensure group members have valid email addresses
4. Verify team creation permissions in Cal.com

​

User Belongs to Another Organization

1. Remove user from current organization
2. Re-provision through SCIM

​

Permission Denied Errors

1. Verify you’re logged in as SAML admin
2. Check email is in SAML_ADMINS environment variable
3. For hosted deployments, verify organization Owner/Admin role
4. Ensure SCIM token has correct permissions

​

Security Best Practices

1. Rotate Tokens: Regularly rotate SCIM bearer tokens
2. Limit Scope: Use minimum required permissions for SCIM token
3. Monitor Logs: Review provisioning logs for suspicious activity
4. Enable HTTPS: Always use HTTPS for SCIM endpoints
5. Validate Requests: Cal.com validates all SCIM requests against schema
6. Audit Events: Track user provisioning and deprovisioning events
7. Secure Database: Ensure SAML database has proper access controls

​

Performance Considerations

​

Initial Sync

• < 100 users: Few minutes
• 100-1000 users: 10-30 minutes
• > 1000 users: May require batching

​

Ongoing Sync

• User creation: 1-3 seconds
• User update: < 1 second
• User deactivation: 1-2 seconds
• Group operations: 2-5 seconds

​

Rate Limiting

1. Reduce sync frequency in IdP
2. Batch operations where possible
3. Contact support for rate limit increases

​

API Reference

​

SCIM Endpoints

​

Authentication

Authorization: Bearer <scim_token>

​

Advanced Configuration

​

Multiple SCIM Directories

Directory 1: Azure AD → HR Department
Directory 2: Okta → Engineering Department
Directory 3: JumpCloud → Sales Department

​

Custom Attribute Mapping

// Example: Map department to team assignment
if (customAttributes.department === "Engineering") {
  assignToTeam(user, engineeringTeam);
} else if (customAttributes.department === "Sales") {
  assignToTeam(user, salesTeam);
}

​

Testing SCIM Integration

​

1. Test User Creation

1. Assign a test user to the application in your IdP
2. Wait for provisioning to complete
3. Verify user appears in Cal.com
4. Check user has correct attributes

​

2. Test User Update

1. Update user attributes in IdP (e.g., name)
2. Wait for sync
3. Verify changes reflect in Cal.com

​

3. Test User Deactivation

1. Unassign user from application in IdP
2. Wait for deprovisioning
3. Verify user loses organization access
4. Confirm user account still exists

​

4. Test Group Provisioning

1. Create a group in IdP
2. Assign users to group
3. Assign group to Cal.com application
4. Verify team is created in Cal.com
5. Confirm group members are team members

​

Related Documentation

• SSO Configuration
• SAML Setup
• Organizations Management
• SCIM 2.0 Specification
• BoxyHQ Directory Sync