Skip to main content
This is separate from our Security Whitepaper (how we protect data) and Compliance Status (certifications). This page answers the network/IT-approval questions specifically.

Domains to allowlist

We don’t yet have static outbound IP ranges to hand you for firewall allowlisting of inbound webhook calls from Workser — our backend runs on managed/serverless infrastructure without a fixed egress IP today. If your firewall requires source-IP allowlisting for webhooks, tell us and we’ll scope a dedicated egress IP for your account rather than promise one that doesn’t exist yet.

Single Sign-On (SSO) and provisioning

Not available today. Authentication is currently email/password and Google OAuth. We don’t yet support SAML/OIDC enterprise SSO or SCIM-based user provisioning/deprovisioning. If SSO is a hard requirement for your rollout, tell your Workser contact — we track this as a roadmap item and prioritize based on real deal requirements rather than a fixed date we can’t commit to yet.

Audit log export

Not available as a self-serve feature today. We don’t yet expose a dedicated security audit log (logins, role changes, deletions) in a SIEM-exportable format. If this is a requirement for your organization, tell us — noted as a roadmap item alongside SSO.

Bring-your-own-cloud (BYOC)

Not available. Workser is a fully-hosted, multi-tenant product. Running Workser inside your own cloud account isn’t offered today.

Status page / uptime

System status

Current status and incident history, self-reported by our team — no uptime percentage published yet, since it isn’t backed by automated monitoring.

Talk to sales or book training

Consulting & Corporate Training

Implementation consulting, team training, and a direct link to book time with sales.

Where we stand today, at a glance

Talk to us about your requirements

If any of the above blocks your rollout, tell us — [email protected].