Role-based workflows
Separate responsibilities across operational roles.
Security & Data Handling
Operational records need controlled access and clean history.
AseTraX separates user roles, keeps audit history, and supports controlled QR token handling so asset movement records stay reviewable.
Security overview
User roles3
Audit eventsReviewable
Role access
Admin
OperatorPICViewer
Audit history
- Asset record reviewed
- Role access updated
- QR token status checked
QR token control
AST-0334-00123ActiveIssued to Operator TeamWhat AseTraX is designed to support.
Audit history
Review events with timestamps and context.
QR token lifecycle
Issue, track, and revoke identifiers.
Session-based access
Use authenticated sessions for protected work.
Offline queue visibility
Keep queued actions visible until sync.
No inflated security claims.
Confidence comes from clear controls and transparent deployment responsibilities, not unsupported badges.
AseTraX does not claim SOC 2, ISO 27001, HIPAA, or similar certifications.
- Focus on practical access and event controls.
- Review hosting and governance responsibilities before rollout.
- Document how the approved deployment handles data.
Security depends on deployment scope.
Application controls are only one part of a responsible operating environment.
Hosting
Choose and document the approved runtime environment.
Database access
Restrict credentials and infrastructure access.
User roles
Apply least-privilege responsibilities.
Backups
Define backup ownership and recovery checks.
Deployment boundaries
Document network, origin, and environment controls.
Support responsibilities
Clarify who manages access, policy, and configuration.
Designed for operational clarity.
Access separation
Different roles receive different responsibilities.
Event history
Important actions retain time and context.
Controlled changes
Operational changes remain reviewable.
Reviewability
Authorized teams can inspect what happened.
Common security questions.
Where is data stored?+
Storage depends on the approved deployment environment and database configuration. It should be confirmed during scope review.
How are roles separated?+
Admin, operator, and PIC workflows use different access responsibilities. Exact permissions should be reviewed for the deployment.
Can logs be reviewed?+
AseTraX records operational audit history so authorized users can review important events and context.
What happens when devices go offline?+
Operator actions remain visible in an offline queue and retry when connectivity returns.
Need to review security requirements before rollout?
Prepare your hosting, access, backup, and governance questions for the deployment conversation.