Administration Guide

Self-Registration

On this page

With self-registration, customers create their own Self Service Portal account from a registration form. A registration creates a Person first and then a customer account for that Person. You choose whether a registration creates them at once or waits until it is approved.

You set up self-registration and review pending registrations in the Settings App. In the Admin Center, each Self Service Portal instance has a Self-Registration tab; the Self Service Portal instances are gated by a configuration right of their own. For accounts that an administrator creates, see Create and Maintain Customer Accounts. For what customers see when they sign in, see Sign In to the Portal.

In the Settings App

The Settings App's Self Service Portal group holds the Self-Registration page. The group is gated by an administrative right of its own: an account without that right does not see the group, unless it holds a right to a node inside it. See Permissions Reference.

Before you begin

  • A Self Service Portal create action of the Person class must exist. Self-registration runs it to create the Person. The action's window shows a Form tab in place of field mapping; the form you build there is the body of the registration form. The window also shows a Template tab. The action's caption always equals its name, and the action has no Condition tab. For workflow actions, see Workflow Overview.
  • A new 2026.1 database created with the Default Workflow contains such an action, New Person (Self-Registration), which is enabled and has a form and a template in the supplied configuration. An upgraded database need not have this action, and an administrator may have changed it; see Default Workflow Configuration.

Set up self-registration

  1. In the Settings App, open Self Service Portal > Self-Registration.
  2. Select Enable self-registration.
  3. To hold each registration until it is approved, select Self-registered accounts must be authorized by the manager.
  4. Set the page's notification check boxes.
  5. In the Workflow group, in Create new Person using Action:, select the Person create action. This setting is required while self-registration is enabled. While self-registration is not enabled, the group is disabled.

The Workflow page of the Self Service Portal group has no node for the Person class; the self-registration action is named on this page instead.

If the chosen action is missing, or is not a Self Service Portal create action, the portal refuses the registration.

Review pending registrations

The Pending registrations group appears on the Self-Registration page when Enable self-registration and Self-registered accounts must be authorized by the manager are both selected. Otherwise it appears only while at least one pending registration exists.

The group's Pending Registrations toolbar offers:

  • Open, which opens the registration in a new window.
  • Approve, which approves the registration. You can also approve from the opened registration.
  • Reject, which deletes the pending registration. A pending registration stored in the format of versions before 7 already names its Person, and Reject deletes that Person as well. For a pending registration in the current format, Reject deletes only the registration.

Approve or reject a registration

  1. Select the registration in Pending Registrations. Use Open to review its details if needed.
  2. Click Approve to create the Person and account, or Reject to remove the pending registration. You can also approve from the opened registration.

What approval does

Approval runs the following sequence automatically:

  1. The Person create action runs and creates the Person. A pending registration stored in the older format that already names its Person skips this step.
  2. A customer account is created for the Person with the password the customer entered at registration.
  3. An e-mail to the Person's primary e-mail address is queued. In it, the password macro reads "Use the password that you specified during the registration."
  4. The pending registration is removed.

If a step fails, for example because the Person has no primary e-mail address, the Person and the account that the approval created are deleted, and the registration stays pending.

How a registration is processed

The Self Service Portal's sign-in form shows the self-registration link only when self-registration is enabled and Windows authentication is off.

The registration form is the form of the Person create action you choose for self-registration, with three required fields in front of it: Login, Password, and Confirm Password. Any attachment area of the action's form is left out of the registration form.

A registration is refused when the e-mail address already belongs to a Person, or when the login already exists as an account or as a pending registration. The password is checked against the password policy before anything is stored.

What happens next depends on whether registrations must be authorized:

  • Without authorization, the Person create action runs and creates the Person, and a customer account is created for that Person with the login and password the customer entered. A registration confirmation is sent to the new Person's primary e-mail address, with the password macro set to the password the customer entered.
  • With authorization, nothing is created yet. The registration is stored as a pending registration and the customer is told to wait. The pending registration does not keep the password in clear text. The Person and the account are created only when the registration is approved, and only then can the customer sign in; see Review pending registrations.

A registration runs as one transaction that is rolled back on any error. The exception is a failure of the Person create action: that transaction is committed so that the error reaches the log.

In both cases, the manager can be sent a notice of the registration when the matching option is on. In the notice of a pending registration, the login, password, and client address macros carry the values from the registration, and the other field macros carry the values of the registration form. For e-mail notifications in general, see Notifications Overview.

A manager notice goes to the primary e-mail address of the manager of the registered Person. When no manager is found, it goes to a fallback recipient address. A pending registration has no account yet, so its notice always goes to the fallback address.