Identity
The configured authentication layer controls access, sessions and recovery.
Server-side credentialsHuman approval boundaries
Security by design
Automation with a brake pedal.
ELUX keeps identity, credentials and sensitive actions behind clear boundaries—so your team can move faster without giving up control.
Sensitive action
Operator approval required
Evidence attached
Secure sign-inTenant isolationProtected credentialsApproval gatesAudit eventsSafe redirectsSecure sign-inTenant isolationProtected credentialsApproval gatesAudit eventsSafe redirects
Three boundaries
Know who. Know why. Know what happened.
Evidence
The operator sees the reason, impact and provider state before acting.
Execution
Credentials stay server-side and sensitive writes respect approval.
Controls
Serious safeguards, explained simply.
Open the detail only when your technical or security review needs it.
Secure identity boundary
Authentication is handled through the configured production identity layer when credentials are present.
Two-factor ready
MFA, recovery and session controls stay inside the secure authentication boundary.
Safe return URLs
Protected redirects only accept local application paths.
No token exposure
Marketplace and provider credentials remain server-side and are never rendered to the browser.
Audit-first operations
Operational actions publish business events for review, insights and future automation.
Tenant isolation
Company-scoped pages resolve one authoritative selected company before loading data.
Approval path
The action waits for understanding.
01
Signal
ELUX detects a material change.
02
Review
The evidence and expected impact are shown.
03
Approve
The configured operator makes the final call.
Move faster without making security invisible.
Review the architecture with us, connect providers deliberately and choose the approval boundary that fits your team.