Design UI for clients trying to access a suspended service

Give your user story a simple, clear title

Description

This links to these AC statements from the Bounce rate epic:

Given my service is suspended, when I access my service, then I cant send emails
Given my service is suspended, when I access my service, then I can view and download my reports for 7 days
Given I access my service, when I see a "suspended" label, then I can contact Notify support to get help

As a Notify client, I need to be able to view my suspended service so that I can investigate my suspended status.

WHY are we building? Suspended services are completely hidden from their owners WHAT are we building? A permission to view reports, past jobs and service status. While blocking sending new messages. VALUE created by our solution Services can investigate why they are suspended.

Acceptance Criteria** (Definition of done)

To be refined through discussion with the team

Given a Notify service is suspended, when service team member logs-in, then they can access and investigate their reports and past jobs Given a Notify service is suspended, when service team member logs-in, then they can't send new messages Given a Notify service is suspended, when service team member logs-in, then they can contact the Notify team

[ ] 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

If this user story emerged from User Research insights:

[ ] Link research insight back to hypothesis from Epic or Objective in Airtable
[ ] Once change/fix/feature is implemented, mark insight as "resolved" in Airtable
[ ] Once change/fix/feature is implements, link insight to design artifacts (Figma) in Airtable
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics

QA Steps

[ ] Tested in a realistic production scenario

cds-snc / notification-planning