No inbound monitoring exposure
The connector calls the broker. The broker and apps do not connect directly to the monitoring interface.
Security
Monitoring access with explicit boundaries.
Server Alerts separates mobile access from private monitoring infrastructure using outbound connector traffic, broker authentication, scoped roles, and auditable operations.
Security model
Protection across the full request path.
Security applies to connector enrolment, broker traffic, identity, membership, commands, and stored credentials.
Outbound HTTPS to broker
Production broker URLs use HTTPS. Plain HTTP is limited to localhost development.
Hashed connector tokens
Connector tokens are hashed and can be rotated from administration controls.
Credential verification stays local
Credentials are verified by the local connector and completed payloads are scrubbed.
Site roles and seat limits
Operators manage supported actions; viewers inspect status. Access is per site.
Audit trail
Invites, roles, settings, enrolments, licences, rotations, and actions are recorded.
Traffic flow
The broker is the controlled meeting point.
Connectors send snapshots and poll command queues. Apps authenticate users, request authorised data, and submit supported actions.
- 1
The connector authenticates to its broker over HTTPS.
- 2
The broker validates user, membership, role, and licence.
- 3
Commands are queued instead of opening an inbound session.
- 4
The connector applies supported actions and reports completion.
Identity
Account security that fits each organisation.
Use built-in account authentication or configured organisation OIDC sign-in.
Organisation SSO
Map approved domains to an identity provider and link existing accounts once.
Multi-factor authentication
Built-in MFA protects password sign-in; federated MFA is handled externally.
Admin separation
Delegate operational administration without granting core system control.