Intermediate Create Account blocker PRD

Until we are ready to service new clients through the manager “Create account” method we want to keep a track record of everyone that wants a Hemi but at the same time make sure that we don’t overload our server with new Hemi db replications.

From Hemi product perspective we want to store all information re the client trying to create a Hemi the same way as we do now (create org, user, etc.) and

1. ensure we don’t flood the server with new DBs until we are ready and
2. make sure we have an understanding of who these clients are as opposed to such accounts that will have a Hemi DB

The differentiation is needed so after this on a “Launch” event from 3C manager portal we can track if we have to open a Hemi OR redirect to a “waiting list” page.

The waiting list page should be a very simple page with a “product card” (to mimic the manager portal) suited as per the solution already prepared by DataSpark below:

The page should have the following elements:

A card in the middle of the screen that has:

1. A back button at the top with the text “Go Back” leading to https://manager.threecolts.com/v2/products
2. Our icon using this one:

1. A Product name of “Hemi” next to the icon
2. Message header under the product name and icon: “Thank you for your interest in our Hemi integration solution!”
3. A description of the current state under the message header: “Currently, Hemi is only available to existing users. We’ve added your email {{email}} to our wait-list. We will send you an invitation soon, stay tuned!” Note: {{email}} is to be picked from the just created org owner. This can be implemented later too and just say “email”
4. The page header in the browser tab is nice to say “Waiting list” but not mandatory

This “waiting list” page should be shown for all new users that have created an account in this period where Hemi is still not publicly available. We should keep storing all info for them (if they create users or anything like this) just ensure we don’t open a Hemi for them until we are ready AND keep everything in order so when we are ready we can create the needed DBs and actually open it up for them