Administration
Groups, areas, members and invitations.
Members
| Name | Callsign | Roles | Status | ||
|---|---|---|---|---|---|
| — |
Create group
Creating a group is a platform action — it needs the
sysadmin role.
Groups
| Name | ID | |
|---|---|---|
No groups yet.
Draw a new area
editing read only
Areas are platform objects — drawing and editing them needs the
sysadmin role. This map shows the areas
linked to the selected group.
Click Draw boundary, then click the map to trace the
outline. The centroid is calculated automatically and sent as
lat/lon.
Click the map to place points, double-click (or press Finish) to close the shape.
Esc cancels.
Drag the handles to reshape the boundary, or
to start over.
Areas
| Name | Centre | Group | Actions |
|---|---|---|---|
| Linked Not linked |
—
|
No areas defined yet.
Pending invites
| Roles | Status | Expires | Created | ||
|---|---|---|---|---|---|
No invites for this group yet.
The one-time code is only ever shown when the invite is created, and it is
stored hashed — so it cannot be looked up or re-sent. Resend
issues a new code and a new expiry, and the previous one stops working.
Devices
Secret for — copy it now.
It is stored hashed and cannot be shown again.
| Name | Reports as | Node id | Last fix | Trust | Battery | |
|---|---|---|---|---|---|---|
| — |
No devices registered for this group.
A device worn by a member reports as that member, and takes priority
over their phone while it is reporting — which is the point, since a phone
goes quiet where there is no cell coverage. A vehicle or equipment unit is its
own marker and is never merged into anybody's position.
Deactivate a device that goes missing: its positions stop
being accepted at once and its history is kept.