UI Design - Checklist for Search UI

### Access

- [ ] Ensure SBC accounts are able to access MHR (not sure how this is done)

### My Asset Registries / My MHR Dashboard - MOVED TO DESIGN TICKET #14611

- [x] Ensure views of the dashboard display correctly for all SBC User types (MHR + PPR).

- [x] Update title to say Manufactured Home and Personal Property Registries Search

- [x] New wording

- Include fees for PPR searches and maybe MHR searches
- Either text indicating combo search is available through all MH searches and/or have a separate combo search in the selector

- [x] Change behaviour of PPR and MHR section in dropdown (collapse both by default)

- [x] Make sure buttons are correct for SBC (free/client)

- [x] Check if SBC staff need to enter first name or if they can search by Last Name only

- [x] Some visual design updates including text styling, icon update, some spacing

----

### Search Selection List, Lien search, and output - [New Ticket](https://app.zenhub.com/workspaces/design-team-space-6144b1bb15dbac0013e68828/issues/bcgov/entity/14501)

- [ ] Confirm selection behaviour and outputs match existing MH Online behaviour and update if necessary (or improve if possible)

- [ ] Check display of multiple owners of the same home (active, historical and exempt

- [ ] Ensure only one PPR search fee is applied per unique MHR Number.

- [ ] Update Selection list title and add icon per latest design

- [ ] Update instructional text

- [ ] Update layout of search criteria (e.g., Owner Name)

----

### Payment - [New Ticket](https://app.zenhub.com/workspaces/design-team-space-6144b1bb15dbac0013e68828/issues/bcgov/entity/14608)

- [x] Ensure fees for SBC MH search, and combo search are correct

- [ ] Use SBC Staff payment interaction (POS) - currently payment is not working

- [ ] *Confirm we enabled payment for SBC accounts - end to end (e.g., it shows up in the account transaction history with the correct labelling, amount, date, etc.)
- [x] *Confirm we did payment error handling for SBC account - works for PPR, need to check for MHR

----

### BC Registries Dashboard

- [ ] Update wording of MHR tile to remove "register" for pilot

----

### Registries Account - [New Ticket](https://app.zenhub.com/workspaces/design-team-space-6144b1bb15dbac0013e68828/issues/bcgov/entity/14610)
- [ ] *Make sure MHR selection tile is displayed for all Premium accounts (or just Pilot accounts) - blocker for Market launch, but not for pilot
- [ ] * Set-up user access to MHR for Pilot users - they will need to also have the PPR product to pilot
- [ ] Check wording - update if needed
- [ ] Need to have a plan for how to update pilot user accounts after pilot is complete and MHR account types are rolled out.
- [ ] Check with Thor & relationships - what is the best solution to enable just one user from a single BCeID to view MHR w/o everyone else in the org viewing it? - Not needed - solution is to ask D&D to create another account for piloting purposes
- [ ] MHR Search Only user exists, but MHR only views do not
- [ ] Make sure asset tile is showing up

----

### Checklist for Search UI - SBC Account

- [ ] *Make sure MHR selection tile is displayed for SBC account or pilot user - blocker for Market launch, but not for pilot
- [x] * Set-up user access to MHR for Pilot users - they will need to also have the PPR product to pilot
- [x] Check wording - update if needed
- [ ] Ensure SBC users get the correct MHR permissions (what are the correct permissions? Melissa)

### HELP

- [ ] Add MHR help (currently it's PPR Help only)

**Error Handling:**
https://docs.google.com/spreadsheets/d/1UTpFigwN9sj8z9gIGLouCw4XBalHUPYkub7qsNmc4FU/edit#gid=345382686

### UI Bugs:

- UI - Folio Number is not displayed in the search history table when entered from the search results screen - Included in Dev ticket #12498

No source files, tests, or entry points are named. Review the remaining checklist items and linked tickets #14501, #14608, and #14610 first to determine what still belongs here; done means the outstanding access, payment, help, wording, and UI checks are resolved or tracked in the appropriate ticket.

Written by the indexing model from the issue text.