Bu sayfa henüz çevrilmedi — İngilizce sürüm gösteriliyor.
Permission reference: Queues & front desk
Control who can manage patient/customer queues and front desk operations.
11 Tem 2026
Permission Reference: Queues & Front Desk
This table lists all permissions that control access to queue and front desk operations in Usystems.
| Permission | What It Controls | Allowed Actions |
|---|---|---|
| queue.view | View patient/customer queues | Users can see the queue list, patient status, appointment times, and queue metrics. |
| queue.create | Create queue entries | Users can add patients or customers to a queue or create appointments. |
| queue.update | Manage queue status | Users can move patients through queue stages (waiting, in-service, completed), reassign to different staff, and update status. |
| queue.call_next | Call next in queue | Users can select and notify the next waiting patient or customer. |
Related Actions
| Action | Required Permissions | Notes |
|---|---|---|
| Scan queue token | queue.view | QR code check-in (auto-selects patient). |
| View queue dashboard | queue.view | Live monitor of all queues. |
| Generate queue report | report.run | Analytics on wait times and throughput. |
| Assign to staff | queue.update | Route patient to specific provider. |
Which roles typically need these?
- Reception staff → queue.view, queue.create, queue.call_next (for front-desk operations)
- Managers → all queue permissions (for monitoring and adjustments)
- Clinical staff → queue.view, queue.update (to see who is waiting and update status)
- Admin → all permissions (full control)
What happens without these permissions?
Without queue.view, users cannot see the queue or patient list. Without queue.create, users cannot add new patients. Without queue.call_next, users cannot advance patients through the queue.
Bu faydalı oldu mu?