Collect profile information and register users

This is an Early Access feature. To enable it, use the Early Access Feature Manager as described in Manage Early Access and Beta features.

Okta can assist you in collecting profile data from end users before they can access any app integrations which use a specific policy. To configure what data Okta collects:

Before you begin

Super admin access is required to modify profile enrollment policies.

Procedure

  1. In the Admin Console, go to Security > Profile Enrollment.
  2. Under the Actions column for the policy you want to update, select the Edit icon.

  3. In the Profile Enrollment section, click Edit to modify the options:

    • Self-service registration: You can choose one of two options:

      • Allowed: Select this option if you want your end users to be able to self-register their Okta account in your org by clicking the Sign up link on the Sign-In Widget.

      • Denied: Select this option if you want your end users to create their Okta account through another method or if you want to create a progressive enrollment policy.

        • In progressive enrollment scenarios, self-service registration is denied but users are prompted for missing profile attributes the next time they sign in. See New sign-in experience.

        • With the Denied option selected, the Sign up link is hidden on the Sign-In Widget.

      • If you want to allow users to self-register for an app integration but not to your entire org, select Denied in your Default Policy. Then create a new profile enrollment policy specifically for that app with Self-service registration set to Allowed.

    • Email verification: If this checkbox is selected, the end user must verify their account through an automated email sent to the address they provided. Until they complete this step, they can't access the app integrations that use this policy. If this checkbox isn't selected, email verification isn't required to sign in. Email verification is required if your org is using password-optional authentication.

    • Add the user to group: End users are automatically added to all groups listed here. If needed, click Go to Groups to open the Groups page in the Admin Console and manage the groups in your org.

    • Inline hook: To use an inline hook as part of your user registration process, first you must add the hook to your Okta workflow. See Inline Hooks. After the hook has been created, select it from the Use the following inline hook dropdown menu.

      After selecting an inline hook, you can Run this hook:

      • When a new user is created: This trigger occurs during a self-service registration request.

      • When attributes are collected for an existing user: This trigger occurs during a progressive enrollment sign-in request.

      • Both: This trigger occurs during a self-service registration request and also during a progressive enrollment sign-in request.

    • Customize label: The profile enrollment form shown to end users can be customized with a header at the top and a confirmation button at the bottom. Enter the text you want displayed to your end users:

      • Form header: The text at the top of the enrollment form. For example, Sign in or Log in to your personal account.
      • Submit button: The text displayed on the confirmation button. For example Submit or Log in.
  4. Click Save.

Related topics

Select a profile enrollment policy