I'm working on a redesign of a website that has a bit of a complicated registration requirement and I just can't get my head around how best to design the necessary forms/pages.
For context, the existing website lets registered users/companies (interchangeable) post classified ads, and anonymous users can then send enquiries to the owner of the ad.
The new requirement is that a "Company" may have multiple employees/users, similar to the scenario in this question.
The existing registration workflow is:
- User goes to the sign-up page, and enters their company's details + their own name
- Next screen, in a multi-line text input they enter one or more email addresses to be the recipients of enquiries to their ads (usually at least one of these addresses will be their own, but I guess it's possible for none of them to be)
- They optionally enter another email address to sign-up for the newsletter, which may or may not be one of the addresses already entered above
- Confirm T&C's
- Finally, enter a username and password. They can login once the admin approves them and sends them a confirmation email.
The client would prefer that each of these email addresses should potentially be -- but not necessarily -- it's own user-account, grouped as employees of that company.
Also, in addition to the recipients of ad enquiries and newsletters, they want another user to receive invoice related emails.
So far, I figured I will ask the registering user to first enter their company details with the necessary checks to ensure that Company has not already been registered, but then what?
Is it even appropriate for a user to register someone else on their behalf?
I'll be ever so grateful if somebody would describe a process/workflow that once implemented as forms/webpages would be intuitive for the user.