Identity & directories
Connected to the directory you already run.
Native connectors for Google Workspace, Microsoft Entra ID, and Auth0. SAML 2.0 and OIDC for SSO (see /integrations/standards ). SCIM for directory and lifecycle sync. Users and groups are a solved problem.
Named live connectors
Directory-native. Not directory-adjacent.
Three production connectors for the identity stacks mid-market teams actually run. Each one syncs the entities that matter for access governance, and provisions the writes your workflows produce.
Google Workspace
Users, groups, admin roles, org units, domains. Full provisioning and sync. Custom actions for operational workflows — move user to OU, sign out active sessions.
Microsoft Entra ID
Users, groups, group membership. Full provisioning and sync. The Entra surface that backs the rest of your Microsoft estate.
Auth0
Users, organizations, roles. Full provisioning and sync. Matches the way Auth0-first product orgs actually model customers and staff.
SSO and directory sync
The standards that do the work.
Owlie supports OIDC SSO with Google (shared credentials) and tenant-supplied Microsoft, Okta, or custom OIDC providers. SAML 2.0 is part of the standards layer — see /integrations/standards for SAML specifics. SCIM is used for directory and lifecycle sync where the source system speaks it.
If your directory isn't in the list.
If your directory or identity system isn't named above, the in-app connector builder is usually the path — especially for OIDC-based systems. Request a native connector via /integrations/request if one makes sense for more teams than yours.
The directory you already run. Governed by Owlie.
Early access is open. Bring your directory and we'll show you the connector working against it.