Org ID and first-time setup

Each organization has an Org ID that links the web dashboard, the database, and the Sentinel mobile app.

On the fleet map you can copy the Org ID from the dedicated control and paste it into the app so devices enroll under the correct tenant.

When your organization is created in Sentinel, the system assigns a unique identifier called Org ID. It's a small but critical piece of data: it defines which tenant owns your geofences, nodes, operators, history, and billing. Without it, field devices don't know where to report; with it, they're attached to the right dashboard in seconds.

The typical flow goes like this: the administrator opens the fleet hub, finds the Org ID control over the map, and copies it with one click. The operator then installs the Sentinel app on Android, opens initial setup, and pastes the Org ID. The app validates against the backend, downloads the remote configuration for your plan, and is ready to report GPS, receive missions, and trigger SOS. The same Org ID is used to enroll physical nodes against the gateway: one source of truth per tenant.

Treat the Org ID as operational configuration, not as a cryptographic secret—but don't publish it openly either. If someone malicious sees it, your data is not directly compromised (the API enforces authentication), but they get hints about the size and nature of your deployment. For sensitive operations (private security, defense), it's good practice to rotate credentials periodically and review who has dashboard access.

If you ever operate across several organizations (say, a parent company and subsidiaries), the superadmin impersonation flow lets you switch context without signing out. Always confirm the active Org ID in the top bar before editing geofences or billing; a change made in the wrong tenant can confuse the field team.