Updates to the Registration Page

User story

As a Sales Person at OpenFn, I want better Data coming through from the registration screen so that I can communicate better with new inbound sign ups.
As a new user, I want to better understand what data is required of me during sign up (what is mandatory and what is not), AND I want to be able to sign up for support without signing up for Product Updates, so that I form a better opinion of the OpenFn product as I sign up and get the support I need, but not the spam what I don't want.

Details

Several updates requested to the Registration Page:

1. Add red asterisks to mandatory fields Registration (Work email address; First name; Last Name)
2. Add a dialling code to the Mobile Number input - either by adding a country code field to the left, or maybe we just label the field "Contact phone number (include +XX as dialling code)" (leave it as not mandatory, with no asterisk)
3. Add a 'LinkedIn Profile Link' Field, to be identical to the Mobile Number one, labelled: "LinkedIn Profile Link"
4. Split out the checkbox into 2 separate ones for users to accept: (1) "Get (free) help from OpenFn automation experts/solution engineers"; (2) "Contact me with Product Updates"
5. Make the corresponding updates to the OFG Internal Automation Workflow in OpenFn such that: (1) this contact data is pulled through into Slack and Odoo; (2) ONLY add those that accept the 'Product Updates' checkbox to the mailing list in Mailchimp. Check on the logic here with Taylor.

Implementation notes

There may be bigger implications for splitting out the checkbox above in terms of backend logic - in which case we should split this ticket into 2 separate ones. My initial assumption would be that we can leave the current checkbox logic as-is, but re-word it to "Contact me with Product Updates", and introduce a NEW checkbox which captures permission to contact for setup support, which does NOT go to Mailchimp, but DOES go to Slack/Asana/Odoo via the OpenFn internal workflow.

If the user inputs nothing into the Mobile Number or LinkedIn Link fields, we should show "Did not provide" in our backend systems against those fields.

This task should not be considered DONE until:

• The OpenFn Workflow has been updated and the contact details are pulling through

Release notes

User acceptance criteria

GIVEN I am a new user on OpenFn
WHEN I go through the registration page
THEN I should see a new LinkedIn Profile Link Input Field
AND I should see which fields are mandatory or not (denoted by a red asterisk)
AND I should see 2 checkboxes, which allow me to opt in to 'setup support' and 'product updates' separately.

GIVEN I am a Sales Person at OpenFn
WHEN a new user signs up
THEN I should see all the details that the user has inputted, including a 'Did not provide" if they left the non-mandatory fields blank in Slack, over email and in Asana/Odoo

GIVEN I am OpenFn's Mailchimp Instance
WHEN a new user signs up
THEN I should ONLY see their details if they ticked 'yes' to the "Contact me with Product Updates" Checkbox

Start by locating the Registration Page entry point and the OFG Internal Automation Workflow, then trace how registration data reaches Slack, Odoo, Asana, and Mailchimp. Confirm the existing checkbox and contact-field handling with Taylor. Done means the page shows the requested fields and opt-ins, while the workflow forwards contact data and only sends product-update subscribers to Mailchimp.