System status
· refreshed every 5 s ·
Services health check · response time
Change delivery per consumer
Recent activity
Users
MC users of . MCX Admin stores no passwords, keys or certificates.
| Login | Name | MCPTT ID | Template | Status | Device |
|---|
Groups
MCPTT, MCData and MCVideo groups of . Changes reach the group server within seconds; members' devices are notified.
| Group | Type | Members | Services | Protection |
|---|
Templates
Named sets of rights (TS 24.484 profile sections). A user's own rights override its template's.
| Template | Rights | Users |
|---|
Import users
CSV or XLSX. The whole file is checked before anything changes.
Preview
| Change | Record | Detail |
|---|---|---|
| Choose a file to see what it changes. | ||
Summary
- File
- none
A file with errors changes nothing. A clean file is applied in batches, one revision each, which History can roll back.
Activate a device
One link or QR code per device. It works once and expires.
- User
- Expires
- Uses
- once; a new link ends this one
- Holds
- server addresses, identities, trust root, UE initial configuration (TS 24.484). No password or key.
Shown once. Closing this page does not end the link; issuing a new one does.
Choose a user and issue a link.
On the device
- The user sets a password from the one-time IdMS link (Users → Password link).
- Android: scan the QR code in openMCX, or open the link.
- C++ client or dispatcher: mcx-client --config device.json --activate <link> --password-file pw
- The client signs in, and the Credential Service issues its SIP credential.
History
Every change is a revision. Rolling back makes a new revision.
| Rev | When | By | Source | Change |
|---|
Audit
Who did what: sign-ins refused, links issued, activations and every change. No secret is recorded.
| When | By | Action | Target | Revision | Detail |
|---|