Design: Explore solutions for assigning domain managers to new domain

[Katherine-Osos]

Issue description

Currently, whoever requests a domain becomes the first manager of that domain once its approved. And it's up to them to assign other managers. In user feedback, we've learned that sometimes the requester of a domain should not become the manager (e.g. an assistant who was only tasked with filling out and monitoring the request).

We need to explore solutions to accommodate that scenario. The scenario is valid for org model AND non-org model; therefore, we should explore solutions for those in tandem because there may be a solution that works for both.

Acceptance criteria

• Create design that accommodates org model when requester should not be the domain manager
• Create design that accommodates non-org model when requester should not be the domain manager
• Create dev ticket(s) for implementation.

Additional context

Ideas considered so far:

• For org model, do not assign any managers for new requests. Admin will have to assign manager.
  • This may not work well for regular members who have requester permissions. They will be dependent on admins.
• For org / non-org model: Allow requesters to indicate an alternate person to become the first domain manager.
• For org / non-org model: Better messaging about how things work today.
  • Could discourage the scenario where an assistant makes the request if they shouldn't be a manager.
  • Designs

There are pros and cons for all of these ideas and should only serve as a jumping-off point for design. They are not meant to be guidance for final solution.

Slack thread where discussion on this originated.

Links to other issues

No response

[PaulKuykendall]

IN Sprint planning, noted that this may not be essential for launch. Should we pull out of M5? @h-m-f-t and @katypies

[katypies]

Going to defer this for future Org Model work - agreed that this doesn't need to be in for the initial release for requests and member management.