Avendoo® online documentation

Registration codes

Users can register autonomous at the Avendoo® welcome page. This process is protected by a verification code. You can create these codes by means of the registration code wizard. The appropriate users enter these codes on the registration page (see screenshot) in the field Verification.

Further information about the selfregistration for users you find here.

You see in the blue box on the tab Master data in the User wizard of the corresponding user which registration code was used. Furthermore the expiration date and the expiration date extension is shown on the sub tab Master data. These can be maintained by the author if required.

To create a new registration code, click on User management → Registration codes → New registration code. The registration code wizard opens.

There is the mass processing function Delete for registration codes. More information about this function you find under Registration codes: Mass processing functions.

The following functions are available via the context menu of the appropriate registration code title.

Master data

Registration code

Enter the favoured registration code. You can use letters, numbers and special characters.


You can create the code for a certain purpose. Decide if the code serves the login, the API interface or both. Note that, if you select type API interface, you got to enter another configuration.


The type API interface is used for creating users via SSO per SAML, if there are not existing.
There are the attribute “registrationLogin” (default: login) for the SAML configuration. This attribute checks, if the corresponding attribute is contained in SAML and uses this value as login for the new user. Only if this login still isn’t existing, a new user will be created.


Choose the client, for whom the registration code is valid.

Starting date and end date

The validity period of the registration code can be limited. The code is valid from the indicated starting date at 0:00 (midnight) onward until the indicated end date at 23:59 p.m.

Standard for clients

You define by selecting the checkbox, that the code is used as standard value for the client. Multiple allocations per client are possible.


Maximum registration (also type API interface)

Stipulate how many registrations you wish to allow with this registration code. You can select between the following options:

  • Any number of registrations or
  • Entering the number of registrations (if you’ve deactivated the check mark Any number of registrations)
    How many registrations are already existing with a registration code you can see in the context menu of the corresponding registration code or in the last column Registrations in the overview of the registration codes.

Use e-mail address as the username (also type API interface)

With this option, you can determine whether the indicated email address is to be used as the user name. If that option is activated no entry field is shown for the user name in the registration form. Additionally, a further note (“E-mail address is used as user name”) is shown under the entry field “E-mail”. Furthermore set a check mark at the entry field “E-mail”.
Without this option only the standard description (“E-mail address”) is used.

To use the e-mail address as the user name, set the check mark Use the e-mail address.

Generate user login automatically (also type API interface)

With this option you can define if the user logins are generated automatically or are entered from the form. In this case the user can give the user login by himself. Please note that the entry field for the user login must be activated.
If the user login is generated automatically, it consists of the prefix, a five-digit number and the suffix (PREFIX + XXXXX.+ SUFFIX)

User profile (also type API interface)

Stipulate which user profile should be used for the registration.

Double opt-in (also type API interface)

Set the check mark Activate double opt-in, if the learner (participant) should receive a verification e-mail and if he/she should confirm it, before he/she gets a registration e-mail.

Stipulate the e-mail content to be sent to participants. Select Use client setting or an Individual notification (then the source path of the Individual notification will be shown. Further information about creating an Individual notification you find here.)

Permissible domain parts for the e-mail address (also type API interface)

You can use this option to indicate which domain parts are permissible for an indicated email address. If you make no entry, every domain part is permissible.

To define the permissible domain parts for the e-mail address, click on the button Add and enter then the domain parts. If needed, you can delete these domain parts by using the button Delete.

Input fields (also type API interface)

Define the order of the input fields for the user via drag and drop. By setting a check mark you define, if this entry field is shown for the user when registering. By setting the check mark Mandatory you define, if the appropriate input field is mandatory for the user when registering.

The following categories of the input fields are available: General, Billing address and Check boxes (check box for general terms and conditions and for the privacy policy).

Only if you’ve selected the type API Interface, the following input fields are available: User name (+Mandatory information), First name, Last name, E-mail (+Mandatory information), Password and Gender (+Mandatory information).

Permission groups
To stipulate which permission groups you want to assign to the user, click on the button Add permission group, select the favored permission group in the list and confirm your selection via click on the button Select. The assigned permission groups are then liste in a table with the columns Title and Action.

Via click on the recycle bin in the column Action you can remove the assignments.

Expiration date

You can define an expiration date not for the registration code only, but also for the user. Thus the user is timed. At the end of the number of days the access will be inactive. So users can register with the code within an optional period, for example three months, but the access is only 30 days valid.

You can define an expiration date extension under Expiration date. The expiration date extension extends the expiration date if the user registers within the indicated number of days prior to the expiration date. The new expiration date becomes “Today + the indicated number of days.”

Default superior

Stipulate which superior the user receives by clicking on the button Select and confirming your selection. If the superior chosen as the default is changed, the superior of all users with this registration code is changed accordingly.

Pre-assignment of OE

Define the OE for the user.

Pre-assignment of area

Define the area for the user.

Pre-assignment of the group

Define the group for the user.

Pre-assigned company name

Define the company name for the user.

Pre-assigned Street, building number

Define the street and building number for the user.

Pre-assigned postal code

Define the postal code for the user.

Pre-assigned Town/City

Define the town/city for the user.

Pre-assigned Country

Define the country for the user.

Pre-assigned Region

Define the region for the user.

Pre-assigned User defines 10 til 14

Define the defined fields 14 til 14 for the user.