Help & Guides
How to operate clusters and pods from the admin portal.
Who can do what
Two kinds of administrator can sign in here, and they see different things:
If you open a cluster you don’t have access to, the portal shows an Access denied screen rather than a generic error — that means your account isn’t permitted for that cluster, not that something is broken.
Setting admin status
Admin status controls whether a cluster or pod is offered to riders, independent of whether the hardware is online. Open it from the Admin button on the cluster card, or the Admin control on any pod card.
When you change a status you can add an optional reason — it’s recorded in the system event log so other operators understand why. Cluster-level status applies to the whole station; pod-level status affects just one pod.
Note: a pod also reports its own device health (online / degraded / offline). That’s separate from admin status — admin status is the availability decision you control; device status is what the hardware reports.
Restart & shutdown
The cluster card has two operational commands sent directly to the device:
Both commands ask for confirmation first. They affect the hardware — they don’t change admin status, so set the cluster to Offline or Maintenance separately if you also want to stop new reservations.
Cluster details & location
The same dialog used for admin status also edits the cluster’s public-facing details: name, description, address, contact phone, and the detail picture shown in the rider app. Leave a field blank to clear it.
Reservations
The reservation list on the cluster page shows every reservation for that cluster across all riders, with status (active, pending, completed, cancelled) and who holds it.
Cancelling or completing a reservation on a rider’s behalf is a Velomodo-admin override. If you’re a cluster admin those buttons will return a permission message — that’s expected.
System event logs
System events are the audit log of everything that happened to a cluster or pod — status changes, door events, connectivity, reservations, and internal sequence events. Open them from System events on the cluster card (whole cluster) or on a pod card (just that pod). Times are shown in your local timezone, newest first.
Use “Load more” to page back further in time.
Reading diagnostics
Diagnostics is a live, read-only snapshot of the three back-end services for a cluster. It has a tab for each. Toggle “Raw JSON” on any tab to see the underlying state verbatim.
Configuration
Configuration (Velomodo admin only) sets per-cluster policies, grouped into three tabs. Edited fields are highlighted and marked “changed” until you save; each tab can be reset to the system defaults.
Hover the ? next to any field in the Configuration and Diagnostics dialogs for a one-line explanation of that specific setting.