v2.4.0 Release: Roles and Permissions

API access is now governed by a clearer role and permission model. Partner accounts receive only the capabilities they need, so integrations can be scoped more precisely without relying on broad, shared access.

What's included?

• Partner accounts are assigned a defined role that determines which API capabilities they can use.
• Access is checked per capability (for example reading data, steering schedules, or managing curtailment pool membership), in addition to existing ownership and group scope checks.
• Dedicated partner roles support common use cases:
  • flex_dispatch — steer group and solar schedules within authorised groups
  • flex_management — manage membership in partner-managed curtailment pools
  • read_p1_user / extended_user — legacy partner roles retained for existing integrations
• Internal Chargee roles (admin, support) remain Chargee-only and are not available for partner assignment.
• Endpoints reject requests when the account’s role does not include the required permission.
  
  This release makes partner access clearer and safer: each integration account can be given the right level of control, while ownership scope and data integrity checks stay in place.