Pages per role
What each kind of user sees. The rule behind every page (decisions D133 and D134): the entity, its state and the next action first; the machinery one click deeper, in the same place on every object. There is no switch for detail: what a person may do follows the role (built in or composed, decision D185) and what a person sees follows the membership's scope (the whole project, or chosen groups, entities and devices, decision D186); a page, a button or a menu entry shows when the role grants its permission key.
One click deeper
The top bar on every page and screen size carries the Smart Parks logo and the product name on the left and, on the right, the theme switch (light, dark or follow the device; kept on the account) and a small health dot for every signed-in account: green while every worker reports and no system alert is open, amber once one has lingered (a worker silent over 15 minutes, a system alert open over 30 minutes), red only after two polls without an answer; a click names the reason and server admins get the way to Server admin, System health.
The entity page has four tabs and the device page five (Settings is the fifth). Overview holds what a ranger needs: the
state, the health, a small map with the newest position, the assignments and the actions.
Data holds the records, positions and events, with the curate, deliveries and provenance
links on each. Connectivity holds what the networks say about the link, per data source: the
connection state, the gateways heard with the best one and its share, signal and frame-counter
gaps for LoRaWAN, the last satellite session for Iridium. Network holds the machinery of that object: identities, traffic, traces and
commands. The tab sits in the URL (?tab=data, ?tab=traffic; network still opens the traffic tab for an old link), so a link from a traffic
row, a gateway or a trace lands on the tab it means. A list shows the columns a person needs
first; the Columns picker adds the rest, per user.
Project viewer (and every role, within its scope)
A viewer sees the pages below. The Operator and Analyst roles see the same pages with more buttons on them (events, control and features; exports, saved views and dashboards); a custom role shows exactly the buttons its keys grant. A member with a scope sees the same pages with only what is in the scope on them.
| Page | Shows | One click deeper |
|---|---|---|
| Live map | Entities with their health (a marker fades as its last fix ages, full colour under an hour and pale by a day, decision D385; a track is faint where it is old and full at its newest fix, decision D386; the selected entity or device is the one with the blue ring and halo, drawn larger; one with a position known to be imprecise, above 50 m, wears a translucent accuracy disc of its radius, selecting it fits the disc in view, and its panel warns; decision D193; on a phone the panels open folded to one line and the layers panel, the feed and an object panel take turns; the battery value in a panel opens the recent voltage trend and reads as "3.72 V · 64%" for a device whose battery type is known, with the chemistry behind the value, decision D248), the layers panel (Entities arranged by group, ungrouped, per type or per type and sub-type; Devices, Features, Events, Coverage; on Events the device's own reports, errors and reboots, are unticked until you tick them, decision D384), tracks with the Tracks card and its length settings (every track shown at once in a colour of its own, kept while others come and go; Tim, 2026-09-21), recent events. The Devices tab is the device layer: every device of the project, off by default, with or without an entity; a device track is dashed. A fence line is drawn in its sections' colours (green live, amber low, red down, grey unknown); its panel shows the line as one bar with a sentence naming what is wrong and where, and points to the fence line page with the sections, the monitors with their voltage charts, the history and the thresholds (phase 32, Fences and traps). Gateways are small dots under the entities, dark green while the network hears them, red when the network reports them offline and grey when it has never seen them, and the layers panel lists them in two groups, online and offline, each switched as a whole (Tim, 2026-09-19); switching heard positions on anywhere shows the gateway layer, and closing the feature hides it again unless you had it on (Tim, 2026-11-08). A click on an entity, a device, a track point or a gateway opens the same kind of panel: the object's state, then links to its page and its Data and Network tabs; a track point shows the fix and the measurements of that moment with its source event and trace, and the position time in an entity or device panel opens that same panel for the newest fix; the panels and the fix panel carry a button that copies the coordinates as "latitude, longitude", and the "Last status" time opens everything the device reported in its newest status, the declared health lines with their levels first, with the way to its source event; a gateway shows the devices it heard and "Show heard positions" narrows the coverage layer to it. Choosing another project fits the map to everything that project's enabled layers hold, its entities and devices, the gateways when the gateway layer is on, its features when they are, so the first thing you see is the reserve you asked for (Tim, 2026-09-21). Coming back to the map within the same project, or reloading the page, opens where you left it, per project and kept on the account, so another browser opens the same view (Tim, 2026-09-20); a "show on map" link switches a hidden object on and keeps it on. The entity and device panels carry the track and heatmap toggles as the same icon buttons as the layers panel's rows, and every tab of the layers panel has one Show all or Hide all toggle beside Fold all. The controls: the green Layers button top left, with the number of layers showing something, and under it the Feed button with the number of alerts and events this account has not seen yet (the feed lists the project's newest events with their alert state, a row centres the map on the event and opens its detail, an open alert can be acknowledged from its row, and a new alert shows a toast with a Show action while the map is open) (the entity, device and event counts live on the layers panel's tabs, the Events page lists the events); the strip top right (base map, 3D terrain under it on a server with a MapTiler key, which also adds the Satellite base map, draw, measure, and the Tracks and Heatmaps buttons only while a track or a heatmap is on); zoom, reset north and Locate bottom right, where Locate follows the phone's position with a dot and an accuracy ring until pressed again (a pan keeps the dot and stops the following). Draw (project admins, and not in the All projects scope, where a feature would have no project to belong to) makes a point, line, polygon or circle into a feature: every tap places a marker, the length, area or radius updates while drawing, vertices can be dragged before the shape is saved, and a circle is kept as a polygon that remembers its centre and radius, named in its panel; a geofence, site or zone offers Create rule from its panel; Measure does the same with Done instead of Save and keeps nothing; a heatmap is switched on per entity or device like a track, from the row's button in the layers panel or the object's panel, and draws where it was over a look-back window, with a settings card for the radius in metres, the sensitivity and the look-back, which is a number of hours or, as a track's length, the time since the device was assigned to the entity; the layers panel, the Tracks card and the object panel open under it from the right edge, from the bottom on a phone | Nothing more |
| All projects (server admins) | The project switcher's first entry: the live map, entities, devices, alerts, events, gateways and traffic over every project, with the project as the top level of the layers panel and a Project column in the lists; links go to the object's own project. Devices in no project appear under "Not in a project" on the device layer and in the devices list's project filter, where a selection can be assigned to a project at once, from each device's first data, with an entity per device if wanted. The other pages stay per project | Only server admins see the entry |
| Entities | Name, type, group, health (the worst of its devices, with that device's battery, movement and temperature line), every device tracking it today by name or "Assign device" for an entity nothing tracks (project admins), last seen from any record of its devices, the last position with its kind (a network estimate, a fixed place, heard by a reader), the open alerts, a map link; the hand-set status is one column away in the column chooser. The list reads itself again every minute. New entity: the type, then a searchable sub-type with its icon (the server's catalogue minus what the project hid under Settings), an optional icon of its own. A selection moves to a group or to another project with a preview of what comes along | The entity page |
| Entity page | The header carries "Edit" and "Move to project…" for project admins; Overview: the entity, its picture (a card of its own, 4:3, set or removed there by project admins; the type icon stays the icon everywhere, decision D194), the small map, the device tracking it with its health, the assignments | Data: positions and events; Connectivity: the link per data source, gateways heard and signal (LoRaWAN), the last satellite session (Iridium) or the frames offloaded and the stations that stored them (offload stations); Network: the traffic and traces of the device tracking it |
| Devices | Name, type, status, serial, entity, group, last seen, health; a selection gets "Create entities…" (an entity per device, named per row, with a type, a group and a start), "Move to project…" (with a preview) and "Analyse performance"; in the all-projects scope "Assign to project" (names per row, a start of choice) and "Move to project…" | The driver column through the Columns picker |
| Device page | The header carries "Tracks |
Assignments (decisions D355 to D358, simplified on 2026-10-26): two plain lists, Project and Entity, the current row first, each row the name and its dates, a job line only while one runs or failed, and who changed a boundary and why; the cards carry "Assign to entity" (an entity of the project or a new one, from the guided start; a device no project holds yet is asked for the project first in the same dialog, and the Project assignments card offers "Assign to project" alone, both for server admins, and "Move to project…" for project admins) and "Release" for project admins; "Edit" on a row for whoever may move its boundaries (a project row: server admin or project admin of every project involved; an entity row: devices:write in the entities' projects) opens a dialog with From and, for a row that ended, To in the project's timezone, "Use the last uplink" beside From, an optional note, and one line saying what else moves (the neighbouring row's edge follows); where the project and the entity changed at the same moment the dialog offers, ticked, to move the other assignment along |
| Alerts, Events | The open alerts and the recent events | Nothing more |
| Commands | The command timelines | Nothing more |
| Data explorer, Exports, Dashboards | The data | Nothing more |
| Movement (Analyze, when the server and the project offer the module) | The list of analyses a person may see; "New analysis" opens the dialog (animals, period, comparison, the method folded); an opened run: cards per animal, the map with tracks and home range, hotspot and cluster polygons, the charts, the table, the warnings, the limitations | Run, Keep, Run again, Cancel and Delete need analysis:run; results are read within the member's scope; "Analyse movement" on an entity page opens the form for that animal |
| Grazing (Analyze, when the module is on) | The list of analyses; "New analysis" opens the dialog (herd, areas from the project's zones and geofences, period, comparison with the period before, the seasons or another herd, weighting); an opened run: cards per area, the map with the areas coloured by relative pressure and the hotspots inside them, the daily animal-hours and use-per-hectare charts, the use-and-rest calendar, the tables, the warnings, the limitations | The same keys as Movement; "Analyse grazing" on a group (Groups page, entities list filter) and "Grazing in this area" on a zone (live map panel, Features page) open the form with it chosen |
| Habitat selection (Analyze, when the module is on) | The list of analyses; "New analysis" opens the dialog (animals, groups, the layers the project offers grouped by source with the ones also squared, period, under Method hrHSA's settings: the available area's quantile, the available points per fix, the thinning, the buffer, the validation, the stop rule); an opened run: a card per animal, the map with the relative selection surface by rank and each animal's available area, the coefficient bars and the Boyce curves, the summary, coefficient, validation and layer tables, the warnings, the limitations; "Make PDF report" | The same keys as Movement; "Analyse habitat" on an entity page opens the form with the animal chosen; the layers a run may name come from the environmental data provider (Server admin), the project's features and the Raster layers card of the Features page (Project admin), where a project admin uploads a GeoTIFF with a band name, a label and its kind, and removes one |
| Network: Traffic, Gateways, Offload, Trace explorer | Not in the sidebar; one device's traffic and traces are on its Network tab (the newest 20 messages of the last 7 days, with a link to all of its traffic). Traffic and the Trace explorer show a device's messages and traces from the time it was assigned to the project alone: a device that came from another project brings none of its messages from there, and one that left takes the later ones with it (decision D359). Traffic and the Trace explorer look back over a window picked from presets, the last hour to the last 2 years (what the server keeps: source events 730 days, failed traces 180, routine traces 30), the newest 200 rows of it; a link with another window in hours keeps working and shows as its own entry (Tim, 2026-10-16: the bare hours field said nothing and stopped at 30 days for no reason the server knew). Offload is the project's LP0 network on one page: the offload stations with their cards, receptions, own report and place, the trackers with their address, whether the keys are set (never the keys), frames, last station and counter, the addresses no device has, and the devices without an address; every row links to the device page where things are set, and a Setup column says what a row still misses; "Make an offload station" turns a device of the project into a station in one dialog (the device, one of the project's or a new one made there, by hand or read over Bluetooth with its LP0 credentials, decision D326; then the entity, the place and the gateway row) for project admins, and "How to set up" unfolds the three steps (phase 42, offload stations). Gateways lists every gateway of the data sources the project's devices use and of the data sources assigned to the project on the Data sources page (decision D235: the assignment adds visibility before any device reports, and never hides a source another project's devices use): the ones that heard the project's devices in the window busiest first, then the silent ones, with a window and a source filter; names and locations come from the platform's gateway list, read daily and on Sync gateways under Server admin, Data sources; a ChirpStack Gateway Mesh relay is listed with a "Relay (mesh)" mark and no receptions of its own, since its uplinks count at the border gateway (decision D237); a project admin sets or changes a gateway's location from its dialog (coordinates, a click on the small map, or the browser's position) when the network gave none (decision D239), and renames it there or from its panel on the live map when the platform's name is the gateway id or a name nobody in the field uses (decision D247; an empty name gives the platform's back) |
Project admins and server admins have the section |
Project admin
Everything a viewer sees, plus the Network section (Traffic, Gateways, Offload, Trace explorer), Rules, Automations, Integrations, Curation and the Project admin section (Members with its Roles and Invitations tabs, the scope picker and the role editor; Features, with New feature, Import and Propose, see features; Groups, Notifications, Settings).
Server admin
Everything, plus the Server admin section (Needs attention, System health, Traffic, Backup and recovery, System alerts, Automations, Notifications, Projects, Users, Devices, Data sources, Gateways, Audit, AI policy, catalogues). The project pages are the same as a ranger's: to check what a ranger sees, sign in as one.
Server admin, Projects lists every project with its organization, slug, timezone and when it was created or archived, with an organization filter, a "Show archived" switch and a New project button; a row opens the project's settings. Two buttons on a row (decision D267): Archive takes a project out of the switcher, the lists and All projects, its members can no longer open it and its rules stop, while everything stays and its devices keep reporting; Restore brings it back. An archived row also offers Delete, which asks for the project's name typed and then removes the project for good with everything that is its own (entities, groups, features, rules, alerts, events, dashboards, members, exports, analyses); devices are server hardware and stay, released from the project, and positions, measurements and traces stay without a project. The audit log keeps both acts with the name.
Server admin, Users lists every account with its active and server admin switches and the open invitations. Its invite form takes one address, a Server admin box and a row per project (project, role built in or custom, what the person sees): one mail with one link, and registration creates every membership at once (decision D190). An address that already has an account gets the memberships straight away and no mail; the form says so and links to the account. A row opens the account's page: the email and name (each with its own Save), the switches (one's own are changed by another server admin), last login and created, a "Send password reset" button that mails the person the same link as the sign-in page's forgot-password, "Add to a project" with a role, the memberships across every project with the role (built in or the project's custom roles), what the member sees (the same scope picker as the project's Members page) and a remove button, and "Delete account" (decision D191): the account, its memberships and sessions go, what the person reported or changed stays without the attribution, the audit trail keeps the deletion; not your own account and not the last active server admin. The project's Members page keeps the project-side view of the same memberships.
Where the machinery lives
- Identities, ports and frames: the device page's Traffic tab (the table first, with the window presets, a type filter, "Problems only" and Load more with the count of the window, every column on a phone with the time staying in view) and Network, Traffic.
- Processing traces: Network, Trace explorer, and the provenance links on a position.
- Provider fields: the source event dialog reached from traffic rows and provenance links.
- Gateways: Network, Gateways, the map's Coverage tab and Server admin, Gateways.
- Offload stations and LP0 trackers: Network, Offload; the Offload station card and the LP0 offload card on the device pages.