Buyer readiness
Controls and verification surfaces for buyers who evaluate seriously.
What’s here
No fake compliance packages
This page is intentionally plain: it points to the real trust docs and explains what LeadIntel controls today, without overclaiming SSO or certifications.
For larger deployments with additional review requirements, contact leadintel@dazrael.com to align on rollout needs and current scope.
Trust docs
Vendor review checklist (questions buyers usually ask)
How is workspace access controlled?
Workspaces are tenant-isolated and enforced by database row-level policies plus membership checks. Roles determine which privileged actions are allowed.
How are changes audited?
Key team-governed actions (members/invites, templates, webhooks, exports, workflow actions) record audit entries without logging secrets or full request bodies.
What identity features exist today?
Authentication uses Supabase email/password sessions. LeadIntel does not claim SSO/SAML/SCIM unless explicitly implemented and enabled.
What governance controls can admins configure?
Workspace admins can set invite domain restrictions, restrict exports by role, and (optionally) require approval before certain handoff deliveries.
How can data leave the system?
LeadIntel supports operational delivery through exports and webhook-based handoff. Payloads are structured and do not expose secrets or tokens.
What does LeadIntel not claim?
No SOC 2 / ISO 27001 claims, no SSO/SAML/SCIM claims, and no “enterprise guarantees” beyond what’s implemented and inspectable in product.