Documentation (directory sync) — Firezone

Cited by

Facts read from this source

• Sync google timing Report an error

  “Google Workspace: User change notifications typically appear within 1–2 minutes, but may take up to 10 minutes. A full sync runs every 4 hours to update groups and memberships and reconcile missed changes.”

• Sync entra timing Report an error

  “Microsoft Entra ID: Microsoft Graph change notifications reflect most changes within moments, backed by a full sync once a day.”

• Sync okta timing Report an error

  “Okta: With an event hook configured, user, group, and assignment changes flow to Firezone as they happen. A full sync runs every 2 hours to reconcile missed changes, or all changes if no hook is configured.”

• Manual full sync Report an error

  “You can trigger a full sync at any time by clicking Sync Now on the directory card in Settings → Directory Sync.”

• Role mapping default Report an error

  “All synced users are assigned the unprivileged User role by default. This role is allowed to sign in from the Firezone Client, but has no access to the admin portal.”

• Automatic role mapping Report an error

  “Automatic role mapping is not currently supported.”

• Deleted user handling Report an error

  “When a user is deleted or suspended in your identity provider, Firezone will delete the associated identity the user signs in with, clearing all active Client and admin portal web sessions for that identity.”

• Google suspended users Report an error

  “Firezone treats suspended, archived, and deleted Google Workspace users as inactive for directory sync.”

• Deleted group handling Report an error

  “When a group or organizational unit is deleted in your identity provider, Firezone will delete the group and all associated Policies. Any access granted by those Policies will be immediately revoked.”

• Nested groups Report an error

  “Firezone syncs nested (sometimes called "transitive") memberships from your identity provider.”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.

Scores citing this record

• The DevOps Engineer Identity, access policy & device posture
• The DevOps Engineer Pricing transparency
• The IT Lead Identity, access policy & device posture
• The IT Lead Deployment, API & administration
• The IT Lead Pricing transparency
• The MSP Technician Identity, access policy & device posture
• The MSP Technician Pricing transparency
• The Operations Manager Identity, access policy & device posture
• The Information Security Officer Identity, access policy & device posture
• The Information Security Officer Pricing transparency
• The Skeptic Identity, access policy & device posture
• The Skeptic Pricing transparency