Skip to content
Markdownllms.txt

Internal Platform Documentation

This guide covers privileges and governance procedures restricted to the Platform Owner organization (SUPER_ADMIN / org_avg_super).

Platform Roles & Governance ​

Who is this for: Platform Administrator (Platform ADMIN) Central Operations Team (Platform SERVICE)


1. Platform Owner Authorization Tier (SUPER_ADMIN) ​

Accounts belonging to the platform owner organization (Advanced Grid Co., Ltd., ID org_avg_super, organizations.type = 'SUPER_ADMIN') have platform-wide tenant visibility (tierOf(authCtx) === 'platform'). Two assignable roles exist at the platform tier (ROLES_ASSIGNABLE.platform):

Role CodeUI LabelCapabilitiesResponsibilities & Restrictions
ADMINPlatform administrator33 / 33Holds every CAPABILITIES entry across every organization, site, meter, invoice, and shared reference table (org.admin, ftrate.write, holiday.write, bank.write, vpn.manage, meter.identity.override, policy.read, invoice.*, telemetry.*).
SERVICECentral operations team9 / 33Monitors meters and HES communications across all sites: view organizations, register/edit/replace meters (meter.write), send connection tests and read-now commands (meter.command), inspect meter IP/port/SIM (meter.network.read), repair 15-minute telemetry (telemetry.sync), view telemetry quality reasons (telemetry.quality.read), manage alarms (alert.manage), view parallel billing comparison (invoice.compare), and read reference rates/holidays (reference.read). (Cannot manage organizations/users, edit tariffs/Ft/banks/holidays, manage VPNs, override meter serials, or issue/approve invoices.)

Six Platform-Admin-Only Governance Capabilities

Although Solar Developer ADMIN accounts manage their own customers, sites, meters, and billing workflows, 6 cross-tenant capabilities remain strictly reserved for Platform ADMIN:

  1. org.admin: Creating/deleting developer organizations, changing organization types, adjusting Active meter limit quotas, moving users/sites across organizations, and inspecting the system-wide Audit log.
  2. ftrate.write: Publishing and updating monthly Ft rates.
  3. holiday.write: Seeding and editing the shared Public holiday calendar.
  4. bank.write: Managing Payment bank accounts (platform defaults and per-developer overrides).
  5. vpn.manage: Creating, editing, enabling/disabling WireGuard, IPsec, and OpenVPN VPN profiles and assigning meters.
  6. meter.identity.override: Overriding a pending/duplicate meter Serial number or confirming an HES-detected meter Swap with a mandatory audit reason (and overriding locked customer countersignatures when authorized).

2. Auditing Live Permissions (GET /api/permissions) ​

  1. Open Settings and select any organization (Platform administration, any Solar Developer, or any Customer company).
  2. Click the People & access tab and select Role permissions.
  3. The portal renders a read-only table served directly by GET /api/permissions from backend-api/src/auth/policy.ts, guaranteeing exact alignment between the UI and API route enforcement across all 3 tiers (platform, developer, customer).

Read-only Role permissions matrix in SettingsFigure 1: Live server-backed Role permissions matrix in Settings.


Next Steps ​

WattDee Platform Admin & Central Operations Manual