Overview · for Administrators

Administer

Manage who can sign in and what they can do, the hub's certificates, license and configuration, and the logs and records you need when something fails.

This section is for the person who looks after a Proxus hub: who may sign in, what each person may see and change, which certificates and license the hub uses, how it is configured, and where to look when something goes wrong. In the hub, Users, Roles and the Certificate Store are in the Security menu. The other screens are in the Platform menu. UNS permissions you also give from Organize > UNS Explorer.

What you manage here

Screen	What it is for
Users	One entry per person or system that signs in. A user gets what its roles allow.
Roles	Sets of permissions: which screens, which kinds of records, which actions, which parts of the Unified Namespace.
My Profile	Your own account: change your password, see your roles.
White Labeling	Your own application title and logo, if your license includes it.
License Info	What your license allows and how close each edge gateway is to its capacity.
Certificate Store	The platform's certificate authority, and every certificate for HTTPS, the hub's NATS server, the gateways, OPC UA connections and outbound targets.
Copilot Settings	The AI services Copilot answers with, and their API keys. See Set up Copilot.
Config Editor	The hub's configuration file, edited in the browser.
System Logs	Warnings and errors from the hub and every edge gateway, and the support bundle.
Database Health	Size, disk use and retention of the telemetry database. See Monitoring.

Every saved record also has an Audit Trail button that shows who changed what, and when.

Start here

Users and roles Add a user, build a role from another one, and set the password and sign-in rules. Open UNS permissions Limit which sites, areas and devices of the Unified Namespace a role can see. Open Certificates The platform CA, your corporate CA, renewal, OPC UA trust and the hub's HTTPS certificate. Open License Read your entitlement and live capacity, activate a key or deactivate a license. Open Configuration Where the configuration file lives, how to change it, and what overrides it. Open System logs Find the warnings and errors behind a problem, from the hub and every gateway. Open Audit trail See who changed a device, profile, rule or user, and the old and new values. Open White labeling Show your own application title and logo instead of the Proxus brand. Open Support bundle Create a cleaned-up package of logs and settings to send to Proxus support. Open

Every connection of the platform can be encrypted with TLS: the hub's HTTPS (port 8443), the NATS links between the hub and the gateways, the gateways' MQTT brokers (port 8883), outbound targets and OPC UA connections. HTTPS and the NATS links are encrypted by default. The plain ports 8080 (HTTP) and 1883 (MQTT) stay open for local access and devices without TLS until you close them: see Security hardening. The certificates for all TLS connections come from the Certificate Store. See Security.

To install, upgrade, back up or secure the installation itself, see Install and operate.

Was this page helpful?

← Previous

Reporting federation

Users and roles

Evaluating Proxus? See it on your own machines in a 30-minute technical session.