Note: These demos are designed for desktop browsers. Some features may not work on mobile devices.
Demo 4 — Environment-Based Role Access

Your environment
is your access.

No user-to-role mapping. No per-request permission checks. Your environment fingerprint determines your key fragment. Change your location, and your access changes automatically.

How It Works
Environment as Role Determinant

In traditional systems, roles are stored in databases mapping users to permissions. XenSplit uses environmental fingerprints that map environments to access levels, not users to roles.

When you're at the office, your environment generates a manager key fragment that can decrypt sensitive data. When you're at home, the same environment generates only a viewer key fragment with limited access.

In a public environment, no valid key fragment is generated, preventing any access to sensitive data.

Current Environment: Home
Network: Home WiFi
Location: Outside Office
Device: Personal Laptop
Environment Fingerprint: a7b3c9d2e8f1...
👔
Manager Access
🔒 Locked
Office Network
Office Location
Company Device
Account Balance: ••••••••
Transaction History: ••••••••
Trading Permissions: ••••••••
Env Key User Key Server Key = Incomplete
👁️
Viewer Access
🔓 Unlocked
Any Network
Any Location
Any Device
Account Balance: $125,432.18
Transaction History: Last 5 only
Trading Permissions: View only
Env Key User Key Server Key = Complete
🚫
No Access
🔒 Blocked
Recognized Network
Recognized Location
Recognized Device
Account Balance: ••••••••
Transaction History: ••••••••
Trading Permissions: ••••••••
Env Key User Key Server Key = Incomplete
How Environment Determines Access
In your current home environment, you only have viewer access. The environmental fingerprint generated from your home network, location, and device maps to viewer-level permissions in the environment database. To gain manager access, you would need to be in the office environment where different environmental factors generate a fingerprint that maps to manager-level permissions.
Why This Is More Secure Than RBAC

Traditional role-based access control stores user-to-role mappings in databases that can be compromised. An attacker who gains access to the database can modify roles or impersonate users.

With XenSplit's environment-based access, the database stores environment-to-role mappings, not user-to-role mappings. There are no per-request permission checks - the environment generates the key fragment needed for access. An attacker can't simply "change" their role without changing their physical environment.

Even if an attacker captures the environmental key from a home environment, it won't work for accessing manager data. The math simply won't allow it.