Skip to main content

Account Creation Preferences

OPSCOMThe Account Creation Preferences feature allows administrators to configure user account creation preferences, choosingchoose between granting users immediate auto-loginportal access or requiring explicit email verification upon registration. UnderstandingIts andprimary setting this preferencepurpose is crucialto for managing your user base effectively, balancingbalance user convenience with system security and data integrity needs.by controlling the onboarding flow. This article is intended for OPS-COM administrators responsible for managing the user registration experience.

Setup and Configuration

This feature is a global system setting that immediately dictates the onboarding workflow for all new users.

PleaseAdmin Side: Administrators must have the appropriate system role permissions to access the configuration menus and modify the registration parameters.

User Side: Depending on the configured preference, new users will either be logged in immediately after creating an account or prompted to check their email for a verification link before they can access the portal. For complete user-side documentation, please refer to the Registering as a User articlearticle.

for

Using this Feature

Administrators can use the user-sidefollowing documentation.instructions to locate the registration setting and toggle the desired onboarding workflow.

Setup & Configuration

Account creation preferences are configured withinConfiguring the UserAccount ProfileCreation settings under System Settings.

Flow
  1. Hover over System Configuration,Configuration, thenclick System Settings,Settings, and click the User Profile tab.

  2. Toggle

    Locate the Auto Login After Register setting,setting.

    which
  3. controls
  4. Enable the accountAuto creationLogin flow.After Register toggle to allow immediate login, or disable it to require email verification.


Available

UsingConfiguration this FeatureStates

The Auto Login After Register setting has two distinct states, each with distinctspecific implications for user experience and system security:

  • Immediate Login (Auto Login After Register: ON)

  • ConfigurationEnabled):: Toggle the Auto Login After Register setting to ON.
  • Behavior: This methodconfiguration allows users to instantly access their account immediately upon completing registration, without requiring them to verify theirbypassing email address.
  • verification
  • Reasonsentirely. toThis Use:method
      reduces
    • Limitedfriction Emailand Access:provides Ideala quicker onboarding experience. It is ideal for scenarios where users might not have immediate access to their email, such as indedicated lobby kiosk setupssetups.

      or for individuals without constant mobile email access.
    • Reduced Friction: Provides a smoother, quicker onboarding experience, especially if your target audience is less tech-savvy or if you aim to minimize any barriers to entry.

Email Verification (Auto Login After Register: OFF)
  • ConfigurationDisabled):: Toggle the Auto Login After Register setting to OFF.
  • Behavior: This methodconfiguration requires users to click a unique verification link sent to their registered email address before they can fully access their account.
  • Reasons to Use:
    • Verifying Legitimate Users: This is generally the preferred methodmethod, as it immediately confirms that the registration originates from a real user with a valid email address, significantly reducing bot registrations orand fake accounts.

    • Account
    Security

    While andimmediate Recovery:login Emailreduces friction, requiring email verification establishes a reliable communication channel from day one. This is crucial for securesecurely processing future password resets, executing account recovery procedures, and sendingdelivering important notifications,system thereby enhancing overall account security.

  • Maintaining Data Integrity: By ensuring valid email addresses from the outset, you improve the quality and accuracy of your user data in the system.
notifications.


Best Practices &and Considerations

  • Balance Securitysecurity and Convenienceconvenience:: Carefully weigh the trade-offs between user convenience (immediate login) and enhanced security/data integritysecurity (email verification) based on your organization's risk tolerance and user base.

  • Communicationtolerance.: Clearly inform users about the account creation process, especially if email verification is required. Provide instructions on checking spam folders for verification emails.
  • Email Deliverability: If using email verification, ensure your system's email sending configurations are robust to guarantee that verification emails are delivered promptly and reliably.
  • Target Audience Analysis: Consider the technical literacy and typical access methods of your target audience when deciding on the preferred setting.

  • ComplianceEnsure robust email deliverability:: SomeIf you require email verification, verify that your system's global email sending configurations are properly established. This guarantees that verification emails are delivered promptly and reliably, preventing users from getting stuck during registration.

  • Communicate the registration process: Clearly inform users about the account creation process on your portal homepage. If email verification is required, provide explicit instructions reminding users to check their spam or junk folders for the activation link.

  • Maintain regulatory compliance: Consider that data privacy regulations mayoften implicitly favor email verificationverification. asForcing itusers to verify their email contributes to better data quality and acts as a verifiable record of user consentconsent.

    verification.