Identity and authentication
Clerk provides the sign-in and session layer. InspectiVault links the authenticated identity to the relevant company or customer membership.
Security and trust
Clear access to the right inspection records.
InspectiVault combines authenticated identity, company membership and server-side permission checks to support separate staff and customer experiences.
Role-based permissions
Platform, company owner, administrator, engineer and customer roles have distinct permissions enforced by server-side guards.
Company and customer context
Data access is scoped using company and customer identifiers so users are served records from their authorised context.
Structured data and file storage
Operational records are kept in the application database, while controlled uploads such as evidence, logos and signatures use object storage.
Activity and report history
Important administrative actions and report lifecycle events can be retained to support review, investigation and accountability.
Issued report integrity
Report review, issue, revision and superseded states help distinguish current output from earlier report versions.
Shared responsibility
Security also depends on how each company operates.
Company owners should give users the minimum access they need, remove leavers promptly, review customer access and maintain their own retention and continuity procedures.
- ✓Use individual accounts rather than sharing credentials.
- ✓Keep roles and company memberships up to date.
- ✓Check recipients before issuing or sharing reports.
- ✓Avoid uploading information that is not needed for the inspection record.
- ✓Report suspected unauthorised access as soon as possible.
Have a security or data question?
Ask about the current architecture, access model or information you intend to manage before committing to a rollout.
This page describes the current application approach. It does not claim independent certification or replace a customer's own risk assessment.