Let contractors help without handing them the keys

Solstice Utilities depends on regional contractors for install and break/fix. Shared SSH keys and a single admin login fail every audit their building owners care about. Locking contractors out forces OEM engineering onto every site visit.

Without Dataplicity

Either contractors get the master keys, or they wait. Nobody can show who accessed which controller after a maintenance window.

With Dataplicity

1. Invite contractors as organisation members with roles scoped to the sites or customers they support - not the whole OEM fleet.
2. Prefer agent-initiated remote access (Remote Shell / Wormhole) over inbound ports and shared bastions when interactive work is required.
3. Keep audit trails for access and support actions so Solstice can answer “who did what” after the visit.
4. Use SSO/SCIM where enabled so joiner/leaver changes follow the contractor firm’s identity process.

Outcome

Contractors can help on the buildings they own operationally - without holding the keys to every Solstice site.

Next

• Support team access
• Audit trails for support
• SSO and SCIM
• Trust on someone else's network

Related: Illustrative customers, Internal IoT operations, Fix a remote site without a truck roll