Security & Governance

Passkeys and 2FA are built into the Omelion access model.

Omelion supports stronger authentication for both internal and portal users so identity is treated as a product concern, not just an infrastructure afterthought.

What It Covers

Passkeys & 2FA

Support stronger authentication for internal and portal users with passkeys, email 2FA controls, and policy-aware access management.

Internal access

Internal users can work with passkeys and optional email 2FA controls.

Portal access

Client portal users can use passkey-based authentication for stronger client-facing login flows.

Admin enforcement

Security settings can shape who must use stronger access controls across the organization.

Operational Signals How this page fits the wider operating model.
TrustAuthentication is part of the platform governance story.
SeparationInternal and portal identity models are distinct but aligned in philosophy.
PracticalityStronger access should not force teams into cumbersome workflows.
Operational Depth

The detail behind this function.

These are the product capabilities that make this part of Omelion feel operationally serious instead of generic.

IdentityWebAuthn-ready access

Passkeys support stronger, cleaner login behavior.

PolicyOptional and enforceable controls

Admins can decide how strong access should be by default.

CoverageInternal and client users

The security model spans both sides of the platform.

VisibilityAuthentication is configurable inside the product

Access control is not buried outside the application.

Next Step Review how passkeys & 2fa fits your recruitment operating model.

Omelion is built for agencies that want their commercial process, delivery work, submissions, portal visibility, and governance connected in one system.