01
Structured records
Each record has defined fields, defined relationships, and a defined role in the business process.
Data & access
Operational objects carry context.
Operational data and access are configured together in L3RA. The records the business actually works on, the operational views different roles need, and the users, roles, and groups that govern access are part of the same layer.
How data is structured
Data shaped around the work.
Records, views, and files connected to records are configured inside the layer. Together they let the system route the work, show it to the right roles, protect it, and update it through the workflow.
02
Operational views
Records are surfaced for different roles and working contexts. The same work can be read through several role-shaped views.
03
Files connected to records
Supporting files stay with the record they belong to — not in a parallel folder structure on the side.
Access context
Access organized by responsibility.
Users, roles, and groups are part of the layer. The same role definitions that govern workflow steps also define who sees which records and views.
01
Users
People allowed into L3RA. Each user belongs to the work through their role — not through a generic account model.
02
Roles
Roles describe what a person does in the workflow. Steps, views, and actions are configured around roles — not around individuals.
03
Groups
Groups collect users who share responsibility: a team, a partner, or a function. Access can be reasoned about at the group level.
04
Identity and sign-in
Configured to match existing policies where applicable. The company keeps its own identity practices intact.
Activity visibility
The record carries its own history.
Records carry the steps taken, the roles that took them, and the context they happened in — without separate tooling on the side.
01
The step that was taken.
Each activity event names the workflow step it belongs to.
02
The role and user that took it.
Activity history is attached to the role responsible at the moment of action.
03
The record that the step applied to.
Activity stays with the record, so the work has its own history.
Shape of a record
What structured means.
A record is what the workflow moves through. It carries the fields the work needs, the relationships it depends on, and the access context that decides who can act on it.
01
Fields
02
Relationships
03
Access context
04
Activity