Appearance
Customer portal
The customer portal is a vendor-branded frontend for the people who operate your deployed product. Customers sign in on your tenant your-vendor.dvcmgr.com host or a configured custom domain.
OEM engineers continue to use the Dataplicity engineering workspace to define device classes, software, streams, and device-page layouts.
Portal and OEM responsibilities
| OEM engineering workspace | Customer portal |
|---|---|
| Define product Device Classes | View assigned product inventory |
| Upload and release class software | Claim and assign devices where permitted |
| Configure stream bindings and page layouts | Open the class-designed device page |
| Operate firmware rollouts | Review device and network connectivity |
| Use engineering diagnostics and remote access | Manage portal users and account security where permitted |
The portal is not a customer route into Remote Shell, the fleet logging cockpit, or firmware rollout controls.
Configure the customer boundary
An organisation administrator configures portal availability, branding, and the tenant or custom domain. Then:
- create customer and site records
- create or select the customer's networks
- invite customer users with the smallest suitable site role
- claim and assign devices
- verify each device's class page
Use dedicated ownership records where enabled. Tags remain useful operational selectors, but they do not replace the portal's customer and network boundary.
Current portal pages
Availability depends on organisation configuration and role.
Overview
The Overview summarises device, network, and user counts. Use Inventory and Networks for operational detail.
Inventory
Inventory lists the devices available to the portal organisation. Permitted users can claim devices and assign them to networks.
A newly claimed device remains dormant until it is assigned to a network. Treat that as an assignment state, not a connectivity failure.
Device
The device page shows identity and connection context. It can also show the OEM-designed class page when class UI is enabled. Live product values on that page come from device class streams.
Network
The network page groups customer devices and shows online and offline context for that deployment boundary. Class boards appear where configured.
Organisation and account security
Administrators manage the portal users, groups, and supported organisation security settings. Individual users manage their account password and multi-factor authentication.
Assign roles
Use customer-scoped roles:
| Role | Typical portal use |
|---|---|
| Site Admin | Manage site structure and devices; configure permitted operational settings |
| Site Operator | Operate assigned devices and acknowledge permitted alerts |
| Site Viewer | Read customer-context inventory without device actions |
Do not invite customer operators as OEM Developers merely to expose a device page. Developer and Engineering permissions include product-wide class and software configuration.
Verify a portal release
Test with representative portal users:
- an administrator who can claim and assign
- an operator who can act on an assigned device
- a viewer who must not see action controls
For each role, verify:
- only the intended customer and networks are visible
- dormant inventory explains the assignment step
- device connectivity agrees with the OEM view
- class widgets show current, missing, stale, and offline states correctly
- engineering-only controls are absent
- sign-out returns to the correct vendor-branded host
Choose a different customer surface
Use a status page when customers only need selected service and incident truth. Use a paired dashboard display for a shared screen. Use the customer portal when named users need to operate their own devices and networks.