01 · Routine resident access
Recognise an eligible resident.
Use the resident’s identity and access eligibility under campus rules. A fresh leave request is not implied for every routine crossing.
Main campus gate · its own entry/exit record
Platform / Security & Access
Connect student identity, permissions and gate records. Give security a clear next step under your university’s rules.
- Identity context
- Configured devices
- Recorded movement
At the gate. A clear next step.
A smoother student journey. An informed security team.
Face recognition · security oversight
Students use a supported face-recognition or QR process. Security oversees access and handles requests that need review.
Security team viewIllustrative product view · sample record
Ananya S.Student ID: FB-1024 · Hostel A · Room 201
Resident- Location / direction
- Main gate · Exit
- Permission
- Approved day-out
- Valid window
- Saturday · 5–8 PM
- University decision
- Approval recorded
- Identity recognised
- Permission checked
- Exit recorded
Main-gate exit recorded · 5 PM
Different locations. Defined responsibilities.
Campus access. Hostel access. Connected records.
02 · Permission-based movement
Apply the relevant permission.
Leave, day-out and late-entry requests follow your approval and timing rules. Hostel access and reporting remain separate from campus entry.
Hostel gate · its own access/reporting processTwo locations, separate events: sample campus return 7:35 PM → hostel reporting 7:42 PM. Your university defines which events are recorded.
When a permission needs review
Give the guard a route. Keep the decision accountable.
Example: an exit request is presented after its permission window ends. Security checks with the responsible university team before proceeding under campus policy.
Security identifies the issue
At 8:10 PM, the guard sees that the day-out window has ended. No exit is recorded at this stage.
The responsible team reviews
The request returns to the authorised approver. In this example, the university approves a revised window until 9 PM.
A valid decision completes the process
Security checks the revised approval. The student then departs and an exit event is recorded at 8:20 PM.
Illustrative approved outcome—not an automatic extension. Without the required approval, security follows the university’s exception procedure.
In the university’s view
Who crossed which gate. With the record to follow.
1,284Main-gate events662 entries · 622 exits
936Hostel-gate events481 entries · 455 exits
6Requests awaiting review4 main gate · 2 hostel gates
Illustrative Saturday · 6 AM–9 PM. Events count crossings, not unique students or current occupancy. Review requests are separate.
Gate events & review contextIllustrative product view · fictional sample records
| Student / hostel | Location | Direction | Time | Permission / context | Record |
|---|---|---|---|---|---|
| Ananya S. · A-201 | Main gate | Exit | 5:00 PM | Approved day-out | Exit recorded |
| Ananya S. · A-201 | Main gate | Entry | 7:35 PM | Day-out return | Entry recorded |
| Ananya S. · A-201 | Hostel A | Entry | 7:42 PM | Hostel reporting | Entry recorded |
| Rohan M. · B-104 | Main gate | Exit | 8:20 PM | Revised window approved | Exit recorded |
Connect the gate setup you use
Your access infrastructure. A planned connection.
QR workflows
Identity and permission checks through the supported QR process.
Face recognition
Supported face devices connect identity and movement events.
Biometric devices
Compatible biometric interfaces support your access setup.
Turnstiles & gates
Supported gate interfaces connect physical access with the configured process.
- 1Device or QR check
- 2Identity & relevant permission
- 3Gate event recorded
- 4Authorised team view
Before rollout
Your IT team and FretBox review device models, interfaces and connectivity, then agree gate locations, permissions and exception responsibilities.
Bring context to campus access.
Explore the student experience, the connected teams and your university’s rules.