Separate team management and service branding

Description

As a Sender, I need to be able to send messages with different branding without creating a whole new team on GC Notify so that I don't waste time doing administrative tasks.

WHY are we building? Currently on GC Notify, creating a service is linked to 2 tasks that don't necessarily need to be linked together: managing a team and 'branding' from where/who the messages are sent. This means that there's potentially administrative work for Senders where there doesn't need to be. Additionally, this linkage may also impact navigation, as Senders have to associate the name of the service with the team in order to manage the team.

For example: Senders need to make a service in EN and another in FR and add the same people to both.

This work would make it easier to implement unified accounts in the future.

WHAT are we building? Allow Senders to create a team and branding separately. Senders can choose to create a number of branding to choose from when they send messages.

VALUE created by our solution Senders save time when they have multiple brands to send messages from.

Acceptance Criteria** (Definition of done)

Given some context, when (X) action occurs, then (Y) outcome is achieved

[ ] Doesn't impact Senders who act as liasons to multiple services (E.g. Nova Scotia)

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