QR Code Role¶
Special role for QR code-based access in calServer V2.
Overview¶
The QR code role is a special user role with limited permissions, optimized for quick access to device information via QR code scans.
Purpose¶
Mobile scanner usage
The QR code role allows staff to quickly retrieve device information without having to log in with full credentials.
Typical use cases:
- Device identification: Scan QR code on device and view master data
- Check calibration status: Next calibration date and current status
- Determine location: Current location and responsible party
- Document access: View latest calibration certificates and test reports
Permissions¶
The QR code role contains only read permissions:
| Operation | Description |
|---|---|
inventory_view |
View device data |
calibration_view |
View calibrations |
dms_view |
View documents |
Restricted access
The QR code role does not allow modifying operations. Users with this role cannot create, edit, or delete data.
Setup¶
Create QR Code User¶
- Navigate to Admin > Users
- Create a new user or select an existing one
- Assign the QR Code role
- Save the changes
Generate QR Codes¶
QR codes for devices are generated automatically and contain:
The QR code can be output in the following ways:
| Method | Description |
|---|---|
| Device label | Direct print on calibration label |
| Report attachment | QR code in calibration certificate |
| Individual print | Separate label print |
Scan Workflow¶
Scan QR code
|
v
Browser opens device page
|
v
Login (if not logged in)
|
v
Display device information
|
+-- Master data
+-- Calibration status
+-- Last calibration
+-- Next due date
+-- Associated documents
Mobile Optimization¶
Responsive display
The QR code view is optimized for mobile devices and displays the most important information in a compact format.
The mobile view includes:
- Device name and inventory number
- Current status with color coding
- Calibration status (valid / expired / due soon)
- Quick access to the latest calibration certificate (PDF)
Security¶
- QR code users must authenticate
- Sessions expire after a configurable period of inactivity
- Access logs are stored for audits