Choose your language

EnglishEspañolPortuguêsFrançais日本語DeutschItalianoالعربيةБеларускаяአማርኛУкраїнськаÍslenskaMagyarAfrikaansČeštinaCymraegHrvatskiMāoriРусскийKiswahiliBosanskiCatalàGalegoGàidhligБългарскиLietuviųTiếng ViệtCebuanoລາວМонголမြန်မာខ្មែរFilipinoBahasa MelayuગુજરાતીBasa JawaTürkçeAzərbaycanՀայերեն繁體中文Euskara简体中文DanskNederlandsहिन्दीSuomiBahasa IndonesiaGaeilgeҚазақшаNorskPolskiRomânăСрпскиSvenskaไทย한국어עברית

Explore TTH Pergola

TTH PERGOLA

Blog

Solar canopy decisions

Who Controls Solar Carport Monitoring Accounts and Remote Access?

Define owner accounts, provider access, exports, staff changes and software responsibilities when handing over solar carport monitoring.

Concept planning desk with a miniature solar canopy, abstract unlabelled charts on a laptop, blank work-order sheets and a weather grid using only sun and cloud pictograms.
Concept illustration: Concept planning desk with a miniature solar canopy, abstract unlabelled charts on a laptop, blank work-order sheets and a weather grid using only sun and cloud pictograms.

Identify account ownership and actual permissions

Monitoring handover is more than sending a username and password. Confirm which organization owns the platform asset, who can add or remove users, which roles only view data and which can change settings or initiate remote operations. Installer access does not establish operator access, and a public dashboard is not equipment administration. DOE solar cybersecurity material highlights access and network considerations, while actual roles depend on the chosen service. Define permissions before assigning people so the installation does not remain tied to one individual's account.

Set boundaries for remote maintenance access

Providers may need remote diagnosis or updates, but specify purpose, authorization, records and revocation after personnel changes. IT, facilities and maintenance teams should assign networking, updates and incident contacts together instead of assuming another party owns them. Verify available authentication, logging and recovery features through the actual service, rather than assuming every platform supports them. Use appropriate supported permissions and controls, reserving consequential settings for authorized people. Passwords do not belong in public documents, screenshots attached to broadly shared tickets or website content.

  • Confirm organizational ownership, administrators and view roles.
  • Define provider access, updates and revocation.
  • Verify exports, recovery and continuity after staff changes.

Test handover against a contractor change

Imagine a campus changing maintenance providers and finding that history is accessible only through the original installer's personal login. Equipment may still operate, but asset management is impaired. During procurement, confirm post-contract access, export formats, account transfer and open-ticket handover, then test agreed owner actions. Avoid discovering at contract end that exports require another service or license. This scenario identifies continuity questions without alleging restrictions by a particular supplier. Platform capabilities and commercial conditions must be verified against the actual arrangement.

Include access review in routine operations

Review permissions after departures, role changes, contractor changes and system upgrades, retaining relevant approvals. Define which data supports maintenance and which reaches public displays, avoiding indiscriminate publication of internal equipment or user information. Recovery contacts should remain accessible to the organization instead of relying exclusively on one employee. Contracts should state platform charges, support duration and consequences of service termination. Good account management does not replace electrical maintenance, but provides a dependable entry point for fault handling, data review and asset transfer.

Is one shared administrator account the easiest handover solution?

It can obscure responsibility and make revocation difficult. Check supported roles and logs, assign access by need, and define who may change settings. Verify recovery, exports and post-contract access rather than relying on one person's password or contact details.

More questions, practical answers →

Continue planning

Topics

Asset account ownershipRole permissionsProvider transition
View system details →Contact TTH
← Blog

Privacy