Your company. Your projects. Controlled access.
Quanavo is built so project information stays inside the right company, the right project and the right permissions. People see what they need to do their job — not everything in the business.
One connected system does not mean open access to everything.
Membership and permissions decide what each person can see and do inside the project.
Company → project → person. Access is granted inward, never assumed.
The right people see the right parts of the job.
Quanavo uses company roles, project membership and permissions to control what each person can see and do. Access is set by the company — users cannot simply give themselves more authority.
Admin
Access to Office and Field with company-level management authority.
Manager
Office access plus the manager experience in Field, within the projects and permissions they have been given.
Field
A focused Field experience for the projects and work they have been assigned.
When Office invites somebody, their company role, project access and permission settings are defined before the invitation is sent. The invited person cannot widen their own access during signup.
Removing somebody from a project removes future access without rewriting the historical record of work they previously carried out.
One company means one independent Company Workspace.
Each business operates inside its own Quanavo workspace. Project information belongs to that company and is not automatically exposed to other Quanavo businesses.
Company data stays separated
Project access is explicitly granted
Cross-company collaboration does not remove ownership boundaries
Where two companies collaborate through Quanavo, each business keeps its own sovereign record. Information is exchanged deliberately rather than silently merging company data.
Project records stay connected to their source.
Documents, evidence, commercial records and project information remain linked to the project they belong to. Quanavo is designed around controlled access and traceable project records rather than loose shared folders.
Private file access
Project files are not intended to be publicly guessable.
Version-aware records
Important project information can preserve current and historical versions instead of silently replacing relied-upon records.
Audit and provenance
Consequential actions retain who changed what and where the information came from where relevant.
Office and Field work from the same project — not separate copies.
The Office web experience and Field mobile experience connect to the same canonical project data. Field can keep a protected local working set when connectivity is poor, then synchronise when connection returns.
Offline Field data is a temporary working set — it does not become a second independent version of the project.
AI helps. It does not take control.
Quanavo can use AI to help organise information, find project context, summarise records and support users. But consequential project decisions remain with authorised people.
AI can help with
- finding permitted project information
- organisation and summaries
- explaining project context
- drafting permitted content
- Quanavo product support
Quanavo AI does not independently
- approve Variations
- approve evidence or inspections
- decide Readiness
- assign work
- release work
- make commercial decisions
- override permissions
Ask Quanavo only works with information the requesting user is permitted to access.
Support does not get invisible access to your projects.
Quanavo Support can explain the product and help users troubleshoot without having unrestricted access to customer project information. Where deeper support access is genuinely required, it must use a controlled, scoped and authorised support process.
No invisible “god mode” into customer projects.
Your project information should not be trapped in Quanavo.
Quanavo supports project and company exports so authorised users can take useful copies of their records outside the system.
PDF · CSV · ZIP, where appropriate to the exported content.
Built with recovery in mind.
Quanavo is designed with backups, recovery procedures and production monitoring so an infrastructure problem does not automatically become permanent loss of project truth.
Recovery must preserve permissions, project relationships and deletion status — not simply restore an old database and reopen access blindly.
A managed cloud foundation for launch.
Quanavo uses managed cloud infrastructure designed to keep company and project data separated, access controlled and project records recoverable. Office and Field work from the same canonical project data rather than separate copies.
Built to connect the job without giving up control.
If you are considering Quanavo for your company and want to understand how access, project data or permissions work, talk to us.