Skip to main content

Registration Settings

Written by Support

The Registration Settings in Wellness360 allow organizations to control how users access and register on the platform. These configurations help ensure that only the right users can onboard, while maintaining security and flexibility based on your organization’s needs.

Follow the details below to understand the different registration types supported and how they work.


Types of Registration Supported

Wellness360 supports multiple registration methods to suit different onboarding requirements:

  • Eligibility-Based Registration

  • Single Sign - On (SSO)

  • Invite-Only Registration

  • Domain-Restricted Registration

  • Open Registration


Eligibility-Based Registration

Eligibility-Based Registration allows only pre-approved users to access the platform.

How it works

  1. The organization uploads an Eligible Users file (CSV) or enables HRIS Sync

  2. These records are stored as eligible users in the system

  3. Only users whose details match this list can register

Verification methods

During registration, users must provide matching details such as:

  • Email + Date of Birth

  • Employee ID + Date of Birth

  • Employee ID + Last Name

  • Email Only

Key behavior

  • Only users present in the eligible records can register

  • Any unmatched user will be blocked from onboarding

  • Ensures controlled and secure access to the platform


Single Sign-On (SSO)

SSO allows users to log in directly using their organization's credentials.

How it works

The organization integrates its Identity Provider (IdP), such as:

  1. Okta

  2. Azure AD

  3. Ping Identity

  4. OneLogin

Users click Login with SSO. Authentication happens via the organization's login system. The platform verifies the user's email domain and identity.

Key behavior

  • Users log in using their work email account credentials.

  • Access can be restricted to specific domains.

  • No manual password creation is required.


Invite-Only Registration

Invite-Only Registration provides controlled onboarding using invitation links.

How it works

  • Eligible user records are uploaded

  • The platform sends invitation emails with unique registration links

  • Only users who receive the invite can register

Key behavior

  • Registration is only possible via the invite link

  • Users cannot sign up without an invitation

  • Even eligible users must be invited to onboard

Best use case

  • Phased rollouts

  • Pilot programs

  • Controlled group onboarding


Domain-Restricted Registration

Domain-Restricted Registration allows users to sign up using their official work email domain.

How it works

  • Admin defines allowed email domains (e.g., @company.com)

  • Users can register using an email address from the approved domain

Key behavior

  • No eligibility file is required

  • System validates email domain during registration

  • Only users with approved domains can access the platform


Open Registration

Open Registration allows users to sign up without an eligibility list.

  1. Admin generates a Group Key

  2. The organization shares the key with users

  3. Users enter the Group Key during registration

Registration details required

  • First Name

  • Last Name

  • Date of Birth

  • Group Key

Key behavior

  • Any user with a valid Group Key can register

  • No pre-uploaded user list is required

  • Suitable for open or large-scale onboarding


Choosing the Right Registration Method

Each registration type serves different needs:

  • Use Eligibility-Based or Invite-Only for strict control

  • Use Domain-Restricted for easy corporate onboarding

  • Use Open Registration for flexible or large-scale programs


Conclusion

By configuring the appropriate registration method, you can ensure a smooth onboarding experience while maintaining the right level of access control and security for your organization.

Need help?
If the issue continues, please contact our Support team at [email protected]. We’ll be happy to assist you and ensure everything is working as expected.

Did this answer your question?