Client Party Code Management

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-12-02. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjIwNjIx)._

Secured Party Code Management should be improved to better serve both Registries Staff and clients who manage registrations in the PPR.
- As a Registries Staff user, I need to be able to look up party names and codes as part of recurring tasks.
- As a client user of the PPR, I want to have a self serve option for managing global changes that would allow me to transfer one party code to another.

Staff use cases include:
- Ensuring there are duplicate names or codes in the system
- Looking up contact/ownership details of the party code
- Adding new parties and codes
- Adding new codes to existing parties (splitting)
- Consolidating codes across different parties to one single party code
- Adding a global change to multiple registrations.

Client use cases include:
- Requesting a new party code
- Changing addresses on existing party codes
- Assigning a new party code to existing and subsequent registrations

Currently a fee schedule is in place, will need a policy review to see how fees will be incorporated into the new tool.

In addition, potentially we could look at whether global changes would need their own verification statements on every registration that is changed, but this question requires a policy review

Note there needs to be a larger conversation across the branch where we look at how to best manage identifying companies across all registries

### Iterations

1. ▶️**build the ability for internal staff to manage secured party codes on behalf of users - with out having to go to IT/ops**

2. Users upload form to form uploader, pay by credit card, then this is queued in Sharon's team's queue to take the next steps

3. self serve users fill out their own application to change the secured party code.. pay and it changes -- Sharon's team might want to approve

### Documentation
[Google folder](https://drive.google.com/drive/folders/1wrfq83lTRhQNJhYnU3LswgJhPlMJfK2E?usp=drive_link)
[Requirements document](https://docs.google.com/document/d/1KZSw1Js0xyykLUinmYP6_lknDgtj32vjdL56xxYomlw/edit?usp=sharing)
[2020 UX Pin Designs](https://preview.uxpin.com/69673cbc47960656bd52dc8ce3567e11f46622d6#/pages/144434788)

Start with the linked Requirements document, Google folder, and 2020 UX Pin designs to understand the proposed party-code workflows. Focus first on the stated internal-staff management iteration, while recording the unresolved fee, verification, and cross-registry policy questions; done requires an agreed scope and acceptance criteria before implementation.

Written by the indexing model from the issue text.