Quick Summary: The SCIM Event Log records every provisioning event SkillsDB receives, including user creation, updates, deactivations, group changes, and career assignments. Use it to verify a sync worked or to diagnose why a user did not appear.
Overview
The SCIM Event Log is an audit trail for every SCIM event that SkillsDB processes. Each row represents one action triggered by your identity provider, the SCIM background sync, or an administrator. Use the event log to:- Verify that a specific user or group change was processed
- Diagnose why a user is missing, deactivated, or has the wrong permission level
- Track permission changes and manager reassignments over time
- Export a filtered audit trail for compliance reporting
Prerequisites
Before using the event log, make sure you have:- Permission level: SkillsDB administrator
- Setup requirement: An active SCIM connection (see SCIM Setup)
- Access requirement: Settings > SSO & SCIM > Configure SSO and SCIM settings, then select Event Log
How to open the event log
1
Open the SSO & SCIM settings
Navigate to Settings > SSO & SCIM and select Configure SSO and SCIM settings.
2
Open the Event Log
In the top right of the page, select Event Log. The event log page opens with the most recent events first.
- Export downloads the currently filtered events as an Excel file (
scim_event_log_YYYY-MM-DD.xlsx) - Refresh refetches the event list
What each column shows
Event types
The event log has ten event types, each representing a specific action. The Event Type filter in the toolbar lets you filter by one or more types simultaneously.Event sources
The Source column shows where the event originated:- Webhook — The event came from your identity provider through Stytch. This is the most common source for real-time provisioning activity.
- Cron Sync — The event came from SkillsDB’s scheduled background sync. This sync retries manager assignments that failed during the initial provisioning and periodically reconciles group memberships.
- Manual — The event was triggered by a SkillsDB administrator action, such as creating or editing a custom SCIM group.
How to filter events
The toolbar above the event table supports four filter types. Filters can be combined.
Filters update the table immediately. Use Export to download the currently filtered results as an Excel file.
How to diagnose a provisioning problem
The event log is the fastest way to find out why a user is missing or has the wrong state. Use these patterns as starting points:Problem: A user who should be in SkillsDB is missing
1
Filter by Event Type: Provisioned
Set the Event Type filter to Provisioned and set a Date range covering when the user was added in your identity provider.
2
Look for the user
If you see a Provisioned event for the user, SCIM created them successfully — check whether they were subsequently deprovisioned. If no Provisioned event appears, the SCIM event for that user never reached SkillsDB.
3
Check your identity provider
In Entra, verify the user is assigned to the SCIM application and belongs to at least one of the provisioning groups. Use Provision on Demand in Entra to push the user immediately. See SCIM Setup and Azure Sync Considerations.
Problem: A user has the wrong permission level
1
Filter by Event Type: Permission and the user
Set Event Type to Permission to see every permission-level change. The Event column shows the old value and the new value.
2
Check group memberships
Filter by the user’s name in a People view filtered by SCIM group membership, or check the Member Added and Member Removed events in the log for that user.
3
Review custom group configuration
If the user is in a custom SCIM group, confirm the group’s permission level in Settings > SSO & SCIM. See SCIM Groups and Permissions.
Problem: A career automation did not run
1
Filter by Event Type: Career Assigned and the user
If the automation ran, there will be a Career Assigned event for the user within the expected time window.
2
Check the automation scope
If the scope is First provisioning only and the user was already a member of the group, the automation will not re-run. See SCIM Career Automations.
3
Confirm the automation exists
Open the custom SCIM group’s edit modal and confirm the automation is still attached and the career still exists.
Common Questions
How long are events kept in the log?
How long are events kept in the log?
SkillsDB retains SCIM event log entries for ongoing audit and troubleshooting. Contact SkillsDB Support if you need to export or purge events for compliance reasons.
Why don't I see events for users who signed in but weren't provisioned via SCIM?
Why don't I see events for users who signed in but weren't provisioned via SCIM?
The SCIM Event Log only records provisioning events. Sign-in activity is separate from SCIM and does not appear in this log. Users who sign in via SSO but were created manually in SkillsDB will not appear here.
Can I see events from before SCIM was enabled?
Can I see events from before SCIM was enabled?
No. The event log starts when SCIM is first configured for your company. Events before that point are not available.
What does a Cron Sync event mean?
What does a Cron Sync event mean?
SkillsDB runs a scheduled background sync to fix manager assignments that couldn’t be made during initial provisioning (because the manager was provisioned after the direct report) and to reconcile group memberships. Events from this background sync are tagged with Cron Sync as their source.
Can non-admins see the event log?
Can non-admins see the event log?
No. The event log is visible only to SkillsDB administrators. Users without admin permission do not see the Event Log button on the SSO & SCIM settings page.
Related Articles
SCIM Setup
Configure SCIM provisioning — the event log populates once SCIM is connected.
SCIM Groups and Permissions
Understand how group membership drives the permission changes you see in the log.
SCIM Career Automations
How Career Assigned events are generated and when they do not run.
Azure Sync Considerations
Known Entra limitations that explain unexpected events (or missing events) in the log.