Appearance
Customer surfaces
Choose the smallest surface that gives customers the intended outcome without exposing internal operations.
| Surface | Use it for |
|---|---|
| Status page | Public service, journey, heartbeat, and incident communication |
| Dashboard display | Shared operational visualisation on a paired screen |
| Customer portal | Authenticated customer workflows on a branded site |
| Support inbox | Conversations linked to customer, device, incident, or service context |
| Documentation site | Product guidance built from an approved documentation repository |
Dataplicity enables these modules for each organisation separately. Your organisation administrator can confirm which modules are enabled for your team.
Launch a customer portal
Where whitelabel sites are enabled:
- Create the site and apply approved branding.
- Connect only the intended customer or portal scope.
- Add a custom domain through the domain-claim flow.
- Publish the required DNS record and wait for verification and TLS activation.
- Test as a customer role with no OEM access.
- Remove connections and revoke the domain when retiring the portal.
Customer provisioning controls, roles, and visible modules must be tested in the portal itself. A group that has OEM console access does not automatically have the same portal scope.
Publish product documentation
Where documentation sites are enabled, an organisation administrator can connect an approved repository, create a documentation site, edit supported content, trigger a build, and review publication state.
Use a dedicated repository and branch with normal pull-request review. Keep secrets, internal runbooks, private API routes, and customer data out of public source. Verify custom-domain ownership and preview the built site before sharing it.
If a build fails, inspect repository access, selected source, content errors, and domain state. Do not edit generated output as the source of truth.
Manage support conversations
The support inbox can receive or create conversations, assign ownership, track waiting or closed state, and link relevant customer and device context. Add the smallest necessary context and avoid copying unrestricted logs or credentials into messages.
Use the incident timeline for acknowledgement and resolution, the RMA record for return status, and the support conversation for customer communication. Linking them does not merge their lifecycles.