Security
Permissions before action. Evidence before acceptance.
Useful AI needs clear limits. Kinemica keeps model recommendations, permission checks and human decisions distinct, with a record of each step.
Practical controls
Know who can do what, and why.
Who can access a workspace?
The operational app is invitation-only. Access depends on current workspace membership and role, with checks on the server and in the database. Assigned workers receive the work and evidence they are permitted to use; an invitation does not grant access to other workspaces.
How are connected devices identified?
An owner registers and pairs a device. Its credential identifies that device and its workspace when it sends a heartbeat, event or image. Expired or revoked credentials are rejected. Pairing alone does not authorise an event workflow or a physical action.
Who can see the evidence?
Evidence files are stored privately. The application checks current access before returning a photograph; knowing its identifier is not enough. Original submissions are preserved, and a later attempt is recorded separately rather than replacing the first image.
What can the AI decide?
AI can assist with observation review and task drafting. Its structured response is validated, but it cannot grant itself permission, bypass a block or approve physical completion. Configured rules and authorised people govern assignment and action. A Routine recommendation is not a safety assessment.
Who accepts completion?
The assigned person starts the work and submits the required evidence. An authorised person then accepts it or requests rework. If the permitted reviewer is also the assignee, the record explicitly says self-confirmation, not independent inspection. There is no automatic after-photo analysis in this workflow.
What does the history establish?
Assignments, decisions, evidence and state changes retain their actors and timestamps. Normal users cannot rewrite audit events. Hash-linked records help check recorded integrity; they do not make an administrator-controlled database absolutely immutable or prove what happened outside the system.
Before an evaluation
Agree the operating scope first.
A controlled evaluation needs named participants, permitted work, evidence access and a person responsible for review. Customer documents or images also require agreed purpose, retention and provider-processing arrangements before use.
Service recovery currently needs operator supervision. A saved request or queued notification is not a promise of immediate processing or confirmed email receipt.
SEE KINEMICA WITH THE FOUNDER
See the decisions alongside the work.
Walk through access, assignment, evidence and acceptance for a relevant workflow.