MeterPilotHow to Share Utility Meter Management Without Losing Control
Assign owners, editors, and viewers deliberately while keeping sensitive identifiers and irreversible actions protected.
Share responsibility, not unrestricted access
Utility management often involves a property owner, family member, tenant, caretaker or staff member. Give each person only the capabilities required for their role.
A practical model uses:
- Owner: controls workspace, membership and consequential settings.
- Editor/operator: manages meters, readings and bills without controlling members.
- Viewer: sees permitted history and reports without changing records.
Decide the property scope
Before inviting someone, identify which properties they need. Access to one workshop should not automatically expose home bills or provider references.
Shared records need server-side authorization on every API route, search result and synchronization payload. Hiding a menu item is not a security boundary.
Protect consequential actions
Membership changes, ownership transfer, account deletion, permanent deletion and entitlement changes deserve explicit confirmation. A cycle should not close merely because an editor entered a reading.
Maintain accountability
An audit history should answer who changed a reading, meter or bill and when. Corrections should preserve enough context to understand the previous value without publicly exposing sensitive data.
Offboarding checklist
- Remove or deactivate access promptly.
- Transfer ownership before an owner deletes their account.
- Revoke device or API tokens where supported.
- Review recent high-impact changes.
- Keep records with the workspace rather than a former member's personal notes.
MeterPilot's team roles support collaboration while keeping workspace ownership deliberate. The account owner remains responsible for choosing members and verifying that each role matches the real relationship.
Match role to task
| Person | Likely need | Should not receive by default |
|---|---|---|
| Caretaker | Add routine readings | Membership or deletion control |
| Accountant | View/export approved records | Meter correction rights |
| Workshop manager | Manage one operational property | Household bills |
| Temporary tenant | View relevant meter history | Other properties or provider IDs |
Use the actual role descriptions shown by MeterPilot; names such as Manager, Operator, Tenant and Viewer are not interchangeable. Review the permission summary before sending the invitation.
Invite safely
Verify the email character by character, set the smallest suitable role and property scope, and send sensitive context separately. An invitation sent to the wrong address should be revoked, not left pending. Never share an owner password or API token as a substitute for membership.
Recheck access after a role change from another session where practical. Interface visibility is helpful, but authorization must also be enforced by the backend for direct API and synchronization requests.
Reserved for Owner, Manager, Operator and Viewer examples using example.com accounts. No unrelated screenshot has been substituted.
Use a portable, role-aware utility history.
Work locally, synchronize when signed in, and export accessible records without flattening property or meter context.
See the MeterPilot workflow