As a Notify admin, we need to be able to move the 'sensitive service' setting into the db so that we can make it configurable via platform setting, and so we don't run out of room in our env files.
WHY are we building?
We could run out of room in our env files to hold all the IDs at some point.
WHAT are we building?
Moving settings to db
VALUE created by our solution
Won't run out of space, can configure settings via Platform Settings
Documentation and Artifacts
Good docs, figma mockups, ADRs, screenshots etc.
Acceptance Criteria
Given a provincial service goes live and needs to be categorized as sensitive, when their go live request is approved, then the sensitive service setting is applied in the database and it is configurable via platform settings.
[ ] Cypress UI tests if needed.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
andrewleith
commented
1 month ago
Description
As a Notify admin, we need to be able to move the 'sensitive service' setting into the db so that we can make it configurable via platform setting, and so we don't run out of room in our env files.
WHY are we building? We could run out of room in our env files to hold all the IDs at some point. WHAT are we building? Moving settings to db VALUE created by our solution Won't run out of space, can configure settings via Platform Settings
Documentation and Artifacts
Good docs, figma mockups, ADRs, screenshots etc.
Acceptance Criteria
Given a provincial service goes live and needs to be categorized as sensitive, when their go live request is approved, then the sensitive service setting is applied in the database and it is configurable via platform settings.
[ ] Cypress UI tests if needed.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics
Related Research Airtable records
QA Steps