Acquia does not currently offer SCIM-based user provisioning. Stepwork automates Acquia provisioning with 98% accuracy — no API required.
No SCIM Support Complexity Vector: Permissions span environments, sites, and content workflows. Removing users can break publishing without UI validation.
Acquia supports complex digital experiences, but AI agents lack orchestration to safely coordinate content changes, deployments, and access across environments. Guardrails are required to prevent automation from bypassing approvals or environment boundaries, which is why teams use Stepwork to automate Acquia flows with 98% accuracy without needing an API.
Acquia supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Acquia does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Acquia 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 Acquia 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 leaving lingering access, increasing security risk. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Acquia 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 via SAML, mirroring your organization's security posture.