Frequently asked questions

Only what an admin has published, through the public surface, and without personal fields. Everything else needs sign-in and the org:contributor role or above.

Through Zitadel, the shared Fleetworks identity provider. There is no self-signup: your first sign-in creates an account with access pending until an admin grants you an Org role.

No. A sync source only reads from the upstream directory. Synced rows are owned by their source; Rolodex never writes back to it.

Active Directory or another LDAP server. Workday and SCIM sources are defined but are stubs today.

The next sync run marks them inactive and keeps the row as a tombstone. Departed users are screened out of every access binding’s desired set.

Only if you set that target’s enforcement to full. The default, additive, applies grants and only reports revokes; report_only changes nothing. Protected principals are never revoked.

Compute HMAC-SHA256 of the X-Rolodex-Timestamp value, a dot and the raw body, keyed with the signing secret returned once when the webhook was created, and compare it with the X-Rolodex-Signature header (sha256=<hex>).

Not yet. The repo has an Expo mobile app and a Tauri desktop shell with manual release workflows, but no release has been published.

No. The plans page shows sample pricing only; use the contact form to ask about access.