{"id":3944,"date":"2021-03-28T17:01:50","date_gmt":"2021-03-28T15:01:50","guid":{"rendered":"https:\/\/pok2.discendum.com\/ohje\/registration\/"},"modified":"2025-07-07T12:59:46","modified_gmt":"2025-07-07T09:59:46","slug":"registration","status":"publish","type":"manual_kb","link":"https:\/\/help.priimalms.com\/en\/ohje\/registration\/","title":{"rendered":"Registration"},"content":{"rendered":"
This help page is for Priima environment administrators<\/div>\n

Registration form<\/h3>\n\n

The environment administrator may create one or more registration forms. Once this feature is enabled, it is possible to register to the Priima environment using a form.<\/p>\n\n

Example of registration form settings:<\/p>\n\n

\"example<\/figure>\n\n
\n

Tip: The text in the Description field can be formatted using the editor, and one or more links can be added to the description field. This allows for linking, for example, to a privacy policy or other necessary website for registered users.<\/p>\n\n\n\n

\"The<\/figure>\n<\/blockquote>\n\n

The form’s mandatory fields are defined using user data fields: the default mandatory fields are First name, Last name and Email address.<\/strong> The mandatory and optional fields of additional data can be changed. If the administrator of the environment has implemented other user data fields, they can also be used for registration. (More information about user data fields on the help page User data fields<\/a>.)<\/p>\n\n

In the settings of the registration form, it is also possible to specify whether the user is to check her own data (ie user data fields) every time or whether she\/he wants to offer the opportunity to register for courses every time.<\/p>\n\n

By default, the registration form shows the logo and description text of the environment’s login page, but you can choose your own image and description for each registration form.<\/p>\n\n

The access level can be specified in the registration form. A different access level can be defined in each registration form.<\/strong> The access level set on the registration form therefore overrides the default set in Management > Access Levels<\/em>view.<\/p>\n\n

The administrator may also choose which course(s) appear on the registration form. This allows self-registered users to choose the course or courses to join as early as the registration stage.<\/p>\n\n

In each registration form, administrator can choose which course or courses it is possible to register through. If there are multiple forms, the administrator can choose which form appears on the environment login page if one of them is desired for such general use.<\/p>\n\n

You can also select a group or groups for the form to which users who register via the form will be directly associated.<\/p>\n\n

If the user is not assigned to or they do not choose any course at the registration stage, they will be guided to the Priima dashboard upon login, which will show a prompt to search for courses in the course catalogue. If dynamic groups are enabled in Priima and a new self-registered user meets the conditions of a dynamic group, they will see a course or courses for that group on their desktop.<\/p>\n\n

Instead of one registration button, several registration buttons can be displayed on the login page: the button’s text will be the name of the registration form.<\/p>\n\n

\n

Tip: Self-registration is also one possible rule in a dynamic group, so dynamic groups can also demonstrate learning to self-registered users.<\/p>\nSee more information about dynamic groups on the page Dynamic Groups<\/a>.<\/cite><\/blockquote>\n\n

Registration to courses via registration form<\/h3>\n\n

The registration form can also be used as a registration form for one or more courses. When creating an account, you can register for suitable courses at the same time.<\/p>\n\n

If the account already exists, even in that situation you can later register for the courses.<\/p>\n\n

Registration to courses via the registration form effectively means joining the course directly. The user will have immediate access to the course contents.<\/p>\n\n

In this situation, you must first log in with your existing account on the registration page and then register for the desired courses via the form.<\/p>\n\n

After logging in, any user data fields in the form are displayed as filled. In this way, the user can check information fields and can also change the existing information, which has been provided during the previous registration or which the administrator of the environment has assigned to the user.<\/p>\n\n

If the user does not remember that he already has an account and enters an email address in the form that already exists as a username in Priima, the user will receive additional instructions by email. The user is told that the account already exists and that he should log in with it and then register again.<\/p>\n\n

The statistics and reports of the registration forms can be monitored in the Priima environment Registration Statistics<\/a> view.<\/p>\n\n

Use of the Personal Identity Code Field<\/h2>\n\n

When the personal identity code field has been enabled in the environment settings, it can also be added as a required field in the registration form. The format of the personal identity code is validated before saving. When a course administrator or environment administrator views a user\u2019s profile in Priima, the personal identity code is not shown by default but must be opened separately to be viewed.<\/p>\n\n

When using registration forms that request a personal identity code, duplicate accounts cannot be created for the same individual. If a matching identity code is already in the system, the user is informed that they already have an account in the environment. They are advised to contact the training organisation for further assistance and to regain access to their existing account. Alternatively, they can try the password reset option on the login page, provided they know the email address linked to their account.<\/p>\n\n

Validity of the accounts<\/h2>\n\n

Registration forms can be used to manage the validity period of user accounts created through it. For each registration form, a certain period of time can be defined, during which the credentials created through it are valid. The validity period can be, for example, 30 days.<\/p>\n\n

The accountss validity period is recorded in the form and it becomes effective for all the accountss that were created through that form.<\/p>\n\n

\"\"
Example of defining the validity period of the username using the registration form<\/figcaption><\/figure>\n\n

Language selection<\/h2>\n\n

When the user creates his own ID in the registration form, language selection happens naturally: The user’s Priima language is saved in the language on which page he registers, i.e. creates his ID. On the registration page, you can choose any language used in Priima. That is, if the language selection is Spanish, the language of the user ID will be Spanish. The user receives e-mail from Priima in that language and can also use Priima in that language. After logging in, he can change the language from the menu in the top bar if necessary.<\/p>\n\n

Customising Emails Sent via Registration Forms<\/h2>\n\n

The default email sent to a registering user can be customised by adding a form-specific message to the email body. The message is placed in the middle of the standard email content, and the full email can be previewed before it is activated.<\/p>\n\n

Similarly, a form-specific message can be created for users registering directly on a course. This message is inserted into the middle of the standard email content.<\/p>\n\n

\"Image
The function Edit the confirmation message is specific to each registration form.<\/figcaption><\/figure>\n\n

Confirmation messages can be edited by language. One tab is used to edit the message sent to registering users, and the other tab is for the message sent to those registering on a course.(Registration to courses means joining the courses directly.)<\/p>\n\n

\"View
A separate confirmation message can be written for both registration and direct course registration.<\/figcaption><\/figure>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":5,"template":"","meta":{"_acf_changed":false,"priimagroup_meta":"This help page is for Priima environment administrators","footnotes":""},"manualknowledgebasecat":[467],"manual_kb_tag":[275,270],"class_list":["post-3944","manual_kb","type-manual_kb","status-publish","hentry","manualknowledgebasecat-login","manual_kb_tag-rekisteroityminen-en","manual_kb_tag-ympariston-hallinnointi-en"],"acf":[],"_links":{"self":[{"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/manual_kb\/3944","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":0,"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/manual_kb\/3944\/revisions"}],"wp:attachment":[{"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/media?parent=3944"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/manualknowledgebasecat?post=3944"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/help.priimalms.com\/en\/wp-json\/wp\/v2\/manual_kb_tag?post=3944"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}