Sign up Page

Design

How it works

Sign up page composition

• Title of the page : “Sign up”

• Introductory text : “

• Sign up Form

Sign up form composition

• Firstname field*

• Lastname field *

• Email field *

  • Plus a tooltip : “Your email will not be shared”

• Password Field *

  • Plus a tooltip a tooltip : “At least 8 characters, including 1 number, 1 capital letter and 1 punctuation mark.”

• Company

• Terms of use Checkbox*

• Sign up button

• I already have an account link that redirect user to the login page

*Mandatory fields

Sign up process

When users clicks on the sign up button after filling the sign up form :

• A confirmation message display

• The user for whom the sign up request was made receives an email informing him that he must validate his email address to confirm his account creation request. At this stage the user is not visible in the list of users to be approved by administrators in the backoffice.

• As soon as the user confirmed his email, the pending account display in administrators’s dashboards in the backoffice.

• A confirmation email is sent to the user to let him know his account request is pending validation.

• Administrators can approve the account or not.

• As soon as the account is approved by an administrator, the user's account becomes active, and the user receives a confirmation by email.

Advanced Configuration

The registration form is automatically generated based on the REST resource for storing account requests.

Adapting the registration form structure

As a default, the REST resource is /data/userregistration which targets the structure userregistration.

You can change the target resource by overriding the default value in config entry $.register.targetPath.

Adding fields to the registration form is done by changing the structure (don’t forget tags that must be added to fields). Please note that the rest_api_include tag don’t need to be added on the structure as it has been explicitly registered in restful services.

Enrich automatically generated form

Based on the structure configuration, the form fields will automatically honour the structure properties description: type, label, compulsoriness, max-length. You can still enrich this default configuration by adding config in portal to fine tune the registration form.

Adding properties to fields description for the targeted structure can be done in $.edit.<targetstructure>.fields

For instance, the default email property in the base configuration is defined as follow:

{
  default: {
    "validators": {
      "email": null,
    },
    "description": {
      "tip-i18n": "signin.loginForm.mail.description"
    }
  }
}

Such configuration will apply a validation rule to the field to check that the value is a valid email address and add a description below the field corresponding to the tip-i18n key.

Disable the accept terms of use

You can deactivate (not show) the “I accept terms of use” checkbox by setting $.register.displayCGU to false

Translations i18n Keys

• I already have an account link : signup.signupForm.cancelButton (i18n)

• Sign up button : signup.signupForm.inscriptionButton (i18n)

• Sign up title : page.title.signup(i18n)

• Introductory text : signup.description(i18n)