Skip to main content
Customer Panel

Run your field communication from one place

The PTTHex Customer Panel is where your organisation manages users, devices, channels, permissions, dispatch, notifications, and day-to-day operations. It runs on your infrastructure, within the capacity your licence covers.

Manage the operating model

Define who can use PTTHex, which devices are approved, and which channels, roles, and policies shape daily work.

What the Customer Panel manages

The panel keeps customer-side administration, operator visibility, and product policy separate from the Client app and the voice media service that carries live audio.

Organization structure

Model branches, departments, groups, users, devices, and channels so communication matches real responsibilities.

User and device approval

A field user can request access from the app, but nothing is granted until an authorised manager in your organisation approves it. Disabled, rejected, and expired accounts stay locked out.

Roles and permissions

Customer roles remain license-scoped and can support owner, security, dispatcher, branch, department, auditor, and operator responsibilities.

Channel and admission policy

Channel updates and live voice access stay tied to current membership, device approval, platform state, and policy checks.

Dispatch and map readiness

Dispatch workflows can cover local map readiness, telemetry policy, SOS routing, presence, device health, geofence policy, and aggregate reporting where licensed and approved.

Status and observability

Operator surfaces are designed to expose redacted status, readiness, and audit context without publishing raw logs, secrets, credentials, internal paths, or sensitive payloads.

Messaging, notices and broadcasts

Manage direct and channel messages, quick notices from a prepared set, and broadcasts. Delivery is tracked honestly through queued, sent, delivered, failed, and retrying, and a failed message is retried within policy rather than reported delivered.

Notifications policy and delivery

Manage providers, registered devices, audience groups, and delivery routing from one place. Provider credentials and device tokens are never exposed in the panel. Emergency notifications take priority over everything else and cannot be muted by personal preferences.

Voice, PTT and calling

Govern push-to-talk channels with admission and emergency preemption, plus the internal and external dialer. Policy and fraud checks can deny a call before it connects, and call history is kept without raw audio.

Zones and geofences

Define map zones, zone rules, and geofences bound to self-hosted map data. Entry and exit apply policy with explainable denials, and rules are versioned and rolled back rather than destructively deleted.

Translation and assistant policy

Set the self-hosted assistant, live translation, captions, and transcription policy. Every workflow is consent-gated and quota-metered within a signed entitlement, and raw audio is not retained.

Capacity and licensing

Your licence sets the ceiling for users, devices, channels, departments, simultaneous speakers, and concurrent sessions. Managers in your organisation can tighten those limits, but nobody can raise them beyond what the licence covers.

Reporting and evidence

Reports built for review and export

Managers get a clear view of operations with personal details removed and access limited by role. Exports carry no credentials, and every report is stamped with the data it was built from so you always know how current it is.

Overview

A filtered summary of customer-local activity across users, devices, channels, and dispatch.

Usage

Voice, calling, and channel usage within the signed license, paginated and streamed for large datasets.

Availability

Service availability with degraded windows surfaced honestly rather than smoothed over.

Incidents

Correlated, prioritized incident records drawn from an immutable, redacted timeline.

Compliance

Versioned policies, consent and retention enforcement, and a redacted evidence pack for review.

Exports

Downloadable outputs that stay redacted and within retention and license policy at all times.

Audit

An immutable, redacted record of admin actions, scoped to the customer's own license.

Honest operational monitoring

A dashboard that tells the truth

The panel dashboard shows real, customer-local status for license, devices, channels, dispatch, incidents, capacity, and readiness. A signal is marked healthy only when its state is genuinely live. Delayed, stale, unknown, degraded, offline, and maintenance states are shown as exactly that, so there is no false healthy.

  • Managers see the true state of their own deployment, not an optimistic summary.
  • Stale positions and unhealthy devices are marked, and clustering never hides an active SOS.
  • Only redacted status summaries are shared upward, keeping raw data on the customer's server.

No false healthy

When a device stops reporting or a session degrades, the panel says so. Honest signals let dispatchers act on what is really happening in the field instead of trusting a green light that no longer reflects reality.

Customer-controlled authority

Managers administer everything on their own server. Local grants can narrow the licensed authority but never expand it, and every change is versioned and reversible with an immutable audit trail. The panel prefers disable, archive, and rollback over destructive deletion, so operations stay under local control without ever rewriting what the license signed.

Designed for customer-controlled operation

The Customer Panel runs on your own server. It uses a signed license, sign-in only with no public account signup, local maps, protected storage for sensitive data, and status views that keep private details out of sight.

  • Checks its own license and stops rather than opening access when a check does not pass.
  • Keeps sensitive data, secrets, and customer information out of anything shown publicly.
  • Uses maps, monitoring, and reporting only within the policy and privacy scope you approve.

Prepare for a panel walkthrough

Share branches, departments, roles, user groups, device approval needs, channel structure, dispatch workflows, reporting needs, and deployment expectations.