Configure Impact Summary Trigger Dates Per Organisation
The Impact Summary Trigger Config infrastructure component exposes organisation-level settings that control when impact summaries are generated (trigger dates), which period types are enabled (annual, half-year, or both), and whether the feature is active for the organisation. Administrators can adjust these settings from the admin interface. This allows organisations to delay the feature rollout, adjust trigger dates to match their fiscal year, or disable the half-year summary if not needed, all without requiring a software release.
User Story
Acceptance Criteria
- Given an administrator updates the annual trigger date for an organisation, when the configured date arrives, then summaries are generated for that organisation's users on the new date
- Given an administrator disables the half-year summary for an organisation, when 30 June arrives, then no half-year summaries or notifications are generated for that organisation's users
- Given an administrator enables the feature for an organisation for the first time, when the next trigger date arrives, then summaries are generated for all eligible users in that organisation
- Given trigger configuration is changed, when the change is saved, then it takes effect for the next scheduled trigger without requiring an app update or server restart
Business Value
Different partner organisations operate on different schedules and have different rollout readiness. Configurable trigger dates prevent the feature from creating noise for organisations not yet ready to use it, and allows alignment with existing reporting cycles — reducing friction during onboarding of new partner organisations.
Components
- Impact Summary Trigger Config infrastructure
- Impact Summary Trigger Service service