Access Controls
Configure organization MFA enrollment, SSO enforcement, domain restrictions and provisioning roles
Z8 controls who can access an organization through its enterprise identity setup: SSO enforcement, domain and invite restrictions, and the role template applied to provisioned users. Each user also manages their own sign-in security.
Not Yet Available
Z8 does not offer IP, location, device, or session access policies. Organizations cannot restrict access by IP address or country, require trusted or managed devices, require hardware-only authenticators, or set session duration, idle timeout, or concurrent session limits.
Organization Access Policy
Organization owners and admins configure the access policy in Settings -> Enterprise -> Enterprise Identity Setup, in the Access Policy step.
-
Complete the Provider, Domain, SSO Configuration, and Test User steps first. The SCIM Provisioning step is optional.
-
In Access Policy, choose the rules that apply to your organization:
Option Effect once activated Require SSO Members can only open the organization in a session that was signed in through the organization's SSO provider. A session started any other way must sign in through the identity provider first. Restrict to verified domain Invite codes can only be redeemed by users whose email address belongs to the enterprise identity domain. Restrict invites Email invitations can only be sent to addresses in the enterprise identity domain. -
Optionally select a Default role template (see below).
-
Choose Save access policy.
-
In Review & Activate, choose Activate enterprise identity.
The rules take effect only after activation. Require SSO also needs the enterprise identity domain to be added and verified in Settings -> Enterprise -> Domain & Branding; activation fails without it.
Avoid Locking Yourself Out
Before activating Require SSO, confirm that your own admin account can sign in through the configured identity provider.
Required Local Authentication
Organization owners and admins can configure Settings -> Identity & Access -> Local MFA on every plan. The policy starts off. An employee-admin role, manager role or custom settings permission does not grant this authority.
Enable the policy and choose 0, 7, 14 or 30 days for future enrollment windows (14 by default). Each day is exactly 24 elapsed hours. Members see their absolute deadline in the organization's timezone, including the zone name. Changing a window affects future assignments only. Disabling suspends enforcement; re-enabling restores existing deadlines. Removing and re-adding a membership, reactivation and retrying approval do not grant a new window.
At the deadline, every interactive human session, including an owner's or administrator's existing session, needs one of these verified routes:
- Password plus a successful TOTP authenticator verification.
- A passkey authentication verified with PIN or biometrics. Synced passkeys qualify.
- A verified sign-in through this organization's currently configured SSO provider. The organization controls MFA at its identity provider; Z8 does not verify the IdP's MFA assurance.
Registration alone, social login, a remembered-device cookie and backup-code recovery do not qualify. Qualifying local verification can be used across organizations in the same session, while each organization's deadline and SSO rules still apply. Require SSO remains independent: local verification is never its fallback, including during an IdP outage. Impersonation does not satisfy an enforced MFA requirement.
Activation and coverage
Every policy change requires owner/admin authority and accepted verification within five minutes. Activation also requires acknowledgment of recovery arrangements. Prepare another administrator who has demonstrated a working route where possible; a registered factor alone does not prove one. A sole administrator may activate after acknowledging the lockout consequence.
The coverage table separates enrolled methods from the last qualifying access to this organization. It shows assigned deadlines and enforcement status. Kiosk-only members are marked outside scope. Coverage never reveals factor secrets, recovery codes, other memberships or activity in other organizations.
Enrollment and recovery
Security verification remains reachable when the organization is blocked. Use it to verify authentication, enroll or replace a factor, sign out or select another permitted organization. First enrollment requires fresh verification of the existing sign-in method. Adding or replacing an existing factor requires accepted verification within five minutes. Passwordless users can use a user-verified passkey; no new password-setup flow is required.
Password plus a valid, unused backup code provides replacement-enrollment access only. Verify a remaining or replacement TOTP authenticator or passkey before returning to the organization. Verify a planned replacement before removing the old method. A lost or compromised last factor can still be revoked: its evidence becomes invalid and no new grace period is granted. Password changes and backup-code recovery clear prior local verification and remembered-device trust.
Recovery has limits
If a sole administrator loses every authentication and recovery route, the organization stays locked. Z8 offers no administrator/support bypass, temporary individual exemption or manual global-factor reset. Organization admins cannot reset another member's account-wide factors.
Deadline assignments, reminders where time permits, and security changes create mandatory email and in-app notices. Notification preferences and tenant email templates cannot remove their required facts. An email delivery failure never extends the deadline. Security events are recorded under the affected organization using the existing audit controls.
Native apps, offline work and independent credentials
Web, mobile and desktop human sessions use the same organization gate. App-login exchanges preserve the authenticated session's evidence. On reconnect, protected clock synchronization and receipt/capability requests pause for verification. Saved clock commands retain their original identity, captured context and timestamps and can resume after verification. The policy does not erase data already cached on an offline device.
Kiosk-only employees, kiosk device/PIN clocking, organization API keys, calendar subscription secrets and report-share links keep their independent authorization and lifecycle. Factor revocation does not automatically revoke those credentials. Interactive kiosk administration remains subject to the human-session policy.
Role Templates
A role template defines the employee role and organization-level team permissions given to a user who is provisioned through SCIM.
Default Role Template
Choose the Default role template in the Access Policy step. The list shows the active role templates owned by your organization and the global templates available to all organizations. Select No default template to clear it.
A SCIM connection cannot be created until a default role template is selected. See SCIM Provisioning.
How SCIM Applies a Template
When SCIM provisions or updates a user, Z8:
- Uses the role template mapped to the user's SCIM Group
externalId, if one exists, and otherwise the connection's default role template. - Sets the user's employee role and organization-level team permissions from the template, and adds the template's default team if it has one.
- Records a
role_template_appliedprovisioning event whenever the applied template changes.
Z8 does not overwrite a role that was assigned manually, through SSO, or through an invite code.
No Template Editor
Z8 has no settings page for creating role templates or group-to-template mappings. Choose from the templates already available to your organization.
Personal Security Settings
Each user manages their own sign-in security in Settings -> Security. These are personal settings, not organization policies.
| Section | What users can do |
|---|---|
| Change Password | Update their password |
| Two-Factor Authentication | Enable or disable two-factor authentication for their account |
| Passkeys | Add and delete passkeys for passwordless sign-in |
| Social Accounts | Connect and disconnect the social sign-in providers enabled for the deployment |
| Active Sessions | Review their sessions, revoke a single session, or choose Revoke All Other Sessions |
Troubleshooting
A member cannot open the organization
Require SSO is active and the member's current session was not signed in through the organization's SSO provider. They need to complete sign-in with the identity provider.
Activation fails with Require SSO selected
In Settings -> Enterprise -> Domain & Branding, add the enterprise identity domain with Add Custom Domain and verify it with Verify. Then activate again.
An invitation or invite code is rejected
Restrict invites or Restrict to verified domain is active. Use an email address in the enterprise identity domain, or change the access policy.