MVP SURF Access Dashboard

This ticket exists to track the functional requirements as we work towards MVP release.
All boxes need to be checked to be ready for public release.
Boxes to be checked by PM

Functional requirements of Access dashboard are described as user stories below.
Relationship to the other stories in this board: If a story does not contribute towards this list, it is nice-to-have for public release. If it contributes directly to functionality in these stories, it is must have for release.
Must have stories: tag with MVP label
All stories with MVP label need to be tested and deployed in release 1.0.0 at the latest.

In the new SURF Access Dashboard, as a (commercial) provider, I want to:

• be able to quickly and independently manage and test a SAML/OIDC application/resource server using dummy identities
• submit data to have a contract drafted by SURF
• promote my application/connection to production environment and set visibility and connectability in catalogue
• grant eduID access to my application/connection
• manage user accounts for my dashboard environment
• receive an email with link to my service when my connection has been put into production
• receive an email when my change request has been implemented in production
• delete my organisation
• edit the name of my organisation

In the new SURF Access Dashboard, as an institution, I want to:

• connect applications to my IdP
• apply authorization rules to services linked to my IdP
• set assurance rules for services linked to my IdP
• set the level of consent for services linked to my IdP
• independently manage and test a SAML/OIDC application/resource server using test identities
• decide whether or not my application/connections are visible in the app catalogue, and decide if institutions are able to freely activate my service, or if I need to give permission
• invite users from outside my organization to register connections for applications that I created
• manage user accounts for my dashboard environment
• edit admin, tech and support contact information as Organisation admin

General

• Implement new design system

To do all the above:

• users should be able to log in to SURF Access Dashboard
• Only CRUD the settings they are authorised for
• view of the navigation is limited to the pages they are authorised for (see line above)