How to stop users from onboarding on your organization

Proper control over user onboarding is an important part of managing any digital platform, especially in financial services where compliance, system integrity, and security are critical. There are situations where an organization may need to temporarily or permanently stop new users from signing up. This could happen during scheduled maintenance, when rolling out new policies, while addressing security incidents, or when conducting internal audits.

If you are using Lendsqr, the admin console provides a straightforward way to control whether new users can onboard into your system. This guide explains how to disable or enable user onboarding, along with additional context and considerations to help you manage this feature responsibly.

Why you might restrict user onboarding

There are several valid operational and security reasons to restrict onboarding:

• System maintenance: During upgrades, deployments, or infrastructure changes, allowing new users into the system may introduce inconsistencies or errors.
• Security concerns: If there is suspected fraud activity or a vulnerability affecting onboarding flows, temporarily disabling access helps contain risk.
• Policy updates: When updating KYC requirements or onboarding criteria, it may be necessary to pause registrations until changes are fully implemented.
• Data integrity checks: During audits or database migrations, limiting new entries ensures consistency and reduces reconciliation issues.
• Controlled rollout: Some organizations intentionally limit onboarding when testing new features or entering new markets.

Understanding these contexts helps ensure that the decision to disable onboarding is deliberate and aligned with operational goals.

Read more: About security checks when onboarding customers

Step by step guide to disabling or enabling onboarding

Follow the steps below to manage the onboarding setting from your Lendsqr admin console.

1. Login to the admin console. Go to the Lendsqr admin platform and enter your authorized credentials. System configuration changes require a Super Admin role.
2. Open Settings. Click the Settings icon (gear) at the top right corner of the admin console.

3. Open System Configuration. In the Settings sidebar, click “System Configuration” under the “Platform” section to expand its categories (Customer Creation Settings, Data and Integration, General, Integrations, Messaging and Notifications, Organization and Business Profile, Payments and Collection, Product, Security, System, and Underwriting and Credit Risk).
4. Search for the relevant setting. Open a category and type a keyword into the “Search” box at the top of that category’s page to filter its settings list directly, rather than scrolling through a long paginated list.

A note on this specific setting: at the time of writing, we could not locate a setting named exactly “Allow User Onboarding” anywhere across all eleven System Configuration categories, despite searching each one with several relevant terms (onboarding, signup, register, allow). This may mean the setting has been renamed, consolidated into another control, or is being phased out as part of ongoing changes to the admin console.

The closest related controls we did find are:

• “Allow Loan Applications” (under System): controls whether customers can request loans. This stops new loan requests, but does not by itself stop new users from creating an account.
• “Allowed Signup Locations” (under Security): restricts sign-up to specific geographic locations rather than turning sign-up off entirely.

If you need to fully stop new user onboarding on your organization and cannot locate an equivalent setting, contact [email protected] to confirm the current mechanism for this on your account.

Verifying the change

After updating the onboarding setting, you should confirm that it behaves as expected. This helps avoid confusion for both internal teams and potential users.

You can verify the change by:

• Attempting a test registration using a new user account.
• Monitoring onboarding logs or system activity if available.
• Checking with your customer support team to ensure no unexpected registrations are occurring.

If onboarding is disabled, new users should not be able to complete the registration process.

Operational considerations

Disabling onboarding is not just a technical action. It has operational and user experience implications that should be considered in advance.

Communication
If onboarding is being disabled for a planned reason such as maintenance or policy updates, inform relevant stakeholders. This may include:

• Customer support teams
• Marketing teams running acquisition campaigns
• External partners or affiliates

Clear communication helps prevent confusion and ensures consistent messaging.

User messaging
Although the configuration controls access, it is also important to consider what users see. Ideally, users attempting to sign up should receive a clear and polite message indicating that onboarding is temporarily unavailable.

Timing
Choose an appropriate time to disable onboarding, especially if your platform has peak usage periods. Doing so during off peak hours minimizes disruption.

Monitoring
While onboarding is disabled, monitor system activity and logs. This helps detect any unexpected behavior or attempts to bypass restrictions.

Security context

Onboarding is one of the most sensitive entry points into a financial platform. It is closely tied to identity verification, fraud detection, and regulatory compliance.

Lendsqr incorporates several security checks during onboarding, including identity validation and risk assessment processes.

Disabling onboarding can be part of a broader security response strategy. For example:

• If unusual onboarding patterns are detected, temporarily stopping new registrations allows time for investigation.
• If third party verification services are unavailable, disabling onboarding prevents incomplete or non compliant registrations.
• If regulatory requirements change, onboarding can be paused until new checks are implemented.

This reinforces the importance of treating onboarding controls as part of your overall risk management framework.

Governance and access control

Because this setting affects the entire platform, it should be governed carefully.

• Restrict access to system configurations to authorized personnel only.
• Maintain an audit trail of who changed the setting and when.
• Establish internal approval processes before disabling or enabling onboarding in production environments.

These practices help maintain accountability and reduce the risk of accidental or unauthorized changes.

Common mistakes to avoid

When managing onboarding settings, a few common issues can arise:

• Forgetting to re enable onboarding after maintenance is complete.
• Not informing customer facing teams, leading to inconsistent communication.
• Assuming the change is active without verification.
• Allowing too many users access to system configuration settings.

Avoiding these pitfalls ensures smoother operations and better user experience.

Managing user onboarding is a critical administrative function that directly impacts security, compliance, and growth. The Lendsqr admin console provides a simple and effective way to control this feature through system configurations.

By following the steps outlined above and applying good operational practices, you can confidently enable or disable onboarding as needed while maintaining system integrity and a positive user experience.