One Brain, and Everyone Sees Their Own View
An employee, a manager, a CFO, and a CISO all open the same platform - and each sees different data and, more importantly, a different set of decisions to make. Self-serve HR for the employee, team approvals for the manager, the cross-domain risk queue for the CFO, the security policy console for the CISO. Role-based dashboards and CORTEX persona lenses reshape one shared model into the right surface for each person.
Illustrative product view
The same brain, four different front doors
The magic isn’t that four people log into one system - plenty of tools do that. It’s that each one lands on a home built for their job, seeing not just different data but a different set of decisions they’re actually the right person to make.
| Role | What they open | What they decide |
|---|---|---|
| Employee | Self-serve HR home | Update details, request PTO, read the pay stub, enroll in benefits |
| Manager | Team view | Approve time off, run reviews, propose comp changes |
| CFO | Cross-domain risk & close queue | Cash, spend, close blockers - the decisions that move the P&L |
| CISO | Security policy console | Agent scopes, enforcement modes, DLP, access reviews |
Role-based dashboards + CORTEX persona lenses
Each role gets a dashboard designed for its job, and the CORTEX persona lens reshapes not just which data appears but which decisions are surfaced first - so a CFO’s home leads with the cross-domain risk queue while an employee’s leads with their pay stub. One dataset, many lenses, and no team looking at a different version of the truth.
Frequently asked questions
Does everyone see the same data?
No - the view is role-scoped. An employee sees self-serve HR, a manager sees team approvals, a CFO sees the cross-domain risk and close queue, and a CISO sees the security policy console. It’s one model, surfaced differently per role.
What is a CORTEX persona lens?
It’s the mechanism that reshapes one shared model into a role’s surface - choosing not just which data appears but which decisions are surfaced first, so each person’s home leads with what’s theirs to act on.
Can an employee see finance or security screens?
Those surfaces are out of an employee’s scope, so they don’t appear in that view. For hard enforcement of who can reach what, pair the persona lenses with your identity provider and Fintra’s policy controls.
How is this different from role permissions in a normal HRIS?
An HRIS scopes HR data by role. Fintra scopes across HR, finance, support, and security on one model, and tailors the decisions each role is asked to make - not just the fields they can read.
Is access control enforced or just hidden in the UI?
Honestly, the persona lenses are how the product scopes the surface per role - the right first line of tailoring, not a substitute for a hardened boundary. Pair them with your identity provider and Fintra’s policy controls for enforced access.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
One brain for people, work, and money
See humans, AI agents, support, and finance decisions in a single governed workspace.
Talk to us