🔒
—
Lockers online
👥
—
Registered users
📦
—
Parcels waiting
🚚
—
Total deliveries
Recent activity
| Time | Locker | Event | User |
|---|---|---|---|
| Loading… | |||
Click an institution to expand its lockers.
Loading…
Loading…
CSV columns: name, unit, phone, email (name required).
Download template
| Name | Unit | Phone | Added | ||
|---|---|---|---|---|---|
| Loading… | |||||
| Locker | Recipient | Registered | Collected | Status | |
|---|---|---|---|---|---|
| Loading… | |||||
📧 Email notifications
⏱ Timings (pushed to all lockers)
Saving timings pushes them to every online locker instantly over WebSocket (applied live + saved on device).
🧹 Maintenance — clear stale data
These permanently remove data. Waiting parcels are kept unless you choose "all".
Defense-in-depth status for your Parcly deployment. No system is ever 100% “unhackable”, but green across the board means the common attack paths are closed.
Security checklist
Loading…
🔓 Access & sign-ins
— who's opening the server
Currently signed in
Loading…
Recent sign-ins & dashboard opens (IP · device)
Loading…
🛡 Controls
📋 Hardening checklist (manual)
- Change the admin password — edit
ADMIN_PASSWORDin.envand theadminaccount. - Serve over HTTPS/WSS — front Parcly with TLS (Caddy/host), set
CLOUD_TLS 1in firmware. - Set a device key — add
DEVICE_KEYto.env+ firmware so only your lockers can connect. - Restrict the dashboard — keep
/dashboardand/api/adminoff the public internet or behind a VPN/allowlist. - Review the Activity Log regularly for failed logins and remote actions.
| Username | Role | Created | Last login | ||
|---|---|---|---|---|---|
| Loading… | |||||
Change my password
| Time | Locker | Event | User | Details |
|---|---|---|---|---|
| Loading… | ||||