Enterprise Features
Webhooks, SCIM, social OAuth, API key status, and organization-level access control
Enterprise features provide advanced capabilities for organizations requiring programmatic access, event-driven integrations, and granular access control.
Enterprise Features
Enterprise-facing capabilities currently center on:
- webhooks for outbound event delivery
- SCIM provisioning for managed identity lifecycle flows
- social OAuth and organization SSO configuration
Operator expectations are split cleanly:
- org-specific credentials are configured in organization settings
- system secrets remain environment-backed
- every enterprise feature remains organization-scoped even when managed centrally by platform operators
For SCIM specifically, keep expectations organization-scoped: organization owners and admins configure it through Enterprise Identity Setup at /settings/enterprise/identity-setup after SSO is configured.
API Keys
Public API Not Yet Available
Z8 does not offer a public API yet. The Better Auth API key plugin is registered and admins can create keys in settings, but no API route accepts a key and no scope is enforced.
Webhook System
Webhooks deliver organization-scoped events to external systems.
Architecture
Delivery Model
- events are emitted with organization context
- matching webhook endpoints are resolved for that organization
- deliveries are queued and retried through worker infrastructure
- payloads are signed with HMAC-SHA256
SCIM Provisioning
SCIM support is part of the enterprise auth stack for provisioning through Enterprise Identity Setup. It should be understood as an organization-scoped integration, not a cross-tenant identity plane.
In practice this means:
- one SCIM configuration provisions one organization at a time
- provisioning activity can map members, role templates, and lifecycle events into that organization
- SCIM setup provides the base URL and bearer token in the wizard, with the token shown only once
- provisioning verification depends on the identity provider pushing a test user or group change back to that organization's SCIM endpoint
Organization Social OAuth
Enterprise organizations can configure their own OAuth providers for branded sign-in and org-aware sign-up flows.
Supported Providers
| Provider | Notes |
|---|---|
| OAuth 2.0 with org-specific credentials | |
| Microsoft | Azure AD / Microsoft identity flows |
| GitHub | OAuth Apps |
| OAuth 2.0 | |
| Apple | Sign in with Apple with additional org config |
Security Features
- PKCE for code-exchange protection
- state signing and nonce validation
- secure cookie-backed web sessions
- organization-aware callback routing
Configuration
# Default social OAuth providers
GOOGLE_CLIENT_ID=<default-client-id>
GOOGLE_CLIENT_SECRET=<default-secret>Organization-specific OAuth credentials, webhook endpoints, and enterprise integration settings should be entered in the product's org settings rather than duplicated as tenant-specific environment variables. Webhook retry and delivery behavior are handled by the application's worker and queue infrastructure, not by separate documented webhook-specific env knobs on this page.