Platform / Security
Control who sees what—without breaking evidence integrity
Security is built into how evidence is generated, shared, and sealed—not bolted on later.
Read-only by default
Hadalian never writes back to your operational systems. We don't move money, change records, or alter history.
Every connection, permission, and share is scoped intentionally to the minimum required access.
Permissions built for real workflows
Different people need different levels of access. Hadalian's permission model reflects that reality.
Internal roles
Owner / Admin
Manages system connections, users, and publication rights.
Contributor
Generates evidence, prepares binders, adds narrative context.
Reviewer
Reviews evidence and drafts without publishing authority.
External roles
Viewer
Read-only access to specific binders or data room materials.
Live Access Participant
Temporary, scoped access to system-derived views for defined periods.
External users never see more than explicitly granted—and never inherit internal privileges.
Invitations with intent
Every external interaction starts with an explicit invitation. No shared passwords. No forwarded links.
Access is always intentional. Silence never implies permission.
Full visibility into access and activity
When evidence is relied upon, knowing who accessed it—and when—matters.
Sealed means sealed
Evidence Binders are immutable once published.
Controlled collaboration
Data Rooms support back-and-forth while remaining governed.
Data handling and residency
Designed to meet the expectations of lenders, auditors, and advisors.
Current
Roadmap
Certification work is driven by what stakeholders expect—not badge collection.