Security
Access is a structural decision, not a setting.
Construction data is commercially sensitive long before it is legally sensitive — margins, claims, incidents, payroll. NESTO treats access as part of the architecture rather than a checkbox on an admin screen.
- Role-derived permissions
- Permissions are generated from each role's navigation. Granting a module in the sidebar grants the view permission; removing it removes the grant. Feature code asks whether a permission is held, never which role is signed in.
- Enforced twice
- Every request is checked at the edge by middleware, then again inside the page it reached. A route added without a middleware rule fails closed rather than open.
- Read-only means read-only
- Roles marked read-only have every non-view grant stripped when permissions are built, whatever a table says. A Viewer cannot reach a create route by typing the URL.
- Company isolation
- A role is held on the membership that joins a person to a company, not on the person. Data is scoped to the company workspace, and one account may belong to several companies with different rights in each.
- Sessions that expire
- Sign-in issues a signed token carrying the company and role, valid for one eight-hour working day. Failed sign-ins return one generic message and never disclose which half was wrong.
- Nothing third-party in the page
- No analytics scripts, no tag managers, no embedded widgets, no external fonts loading at runtime. Your people are the only ones watching your workspace.
Plainly
What we do not claim
NESTO does not yet hold third-party certification, and we will not display a badge we have not earned. What we can do is show you exactly how access control is built and let your IT team judge it. Ask, and we will walk them through it line by line.
01Questions
Security and data.
Where does our data live?
In your company workspace, scoped to your company record. The role that grants access is held on the membership joining a person to that company, so nothing is visible across a boundary it was not granted across.
How is access enforced?
Twice. Middleware checks the session and the role configuration at the edge before a page is reached, and the page checks the permission again itself. A route added without a middleware rule fails closed.
How long does a session last?
One eight-hour working day, then sign-in is required again.
Do you train AI models on our data?
No. V0.1 has no AI features and your data is not used to train anything, by us or anyone else.
What do you load from third parties?
Nothing at runtime. No analytics, no tag managers, no embedded widgets. The page you are reading loads no images and no external scripts.
→One workspace
Bring the whole companyinto one system.
Projects, procurement, quality, safety, people and finance — under one roof, with one set of rights over it.