AddEvent does not currently offer SCIM-based user provisioning. Stepwork automates AddEvent provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Access impacts shared calendars and campaigns. Automation can’t ensure links and embeds are fully revoked.
Without SCIM, AddEvent can’t automatically manage collaborator access as roles change. That leaves admins handling access one user at a time, which is why teams use Stepwork to automate AddEvent flows with 98% accuracy without needing an API.
No. AddEvent does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates AddEvent provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to AddEvent through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is manual work. Additional risks include creating governance gaps, access often persists longer than needed. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in AddEvent with 98% accuracy — in a 15-minute demo.
Book a DemoNo. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider, mirroring your organization's security posture.