Security is part of the operating model, not a premium add-on
LoanDesk Works is designed so company isolation, access control and auditability remain part of the core platform even as subscription plans and modules evolve.
Tenant Isolation
Authenticated company context limits records, reports, files and operations to the correct subscriber workspace.
Role-Based Access
Users receive only the modules and actions appropriate to their assigned role and scope.
Audit Logs
Important actions are attributed to users so changes can be reviewed instead of disappearing silently.
Email Verification
Registration and account recovery use authentication codes sent to the registered email address.
Password Protection
Passwords are hashed rather than stored as readable text, with lockout logic for repeated failed attempts.
Segregation of Duties
Loan approval, disbursement, collections and financial adjustments can be assigned to different roles.
Company01 should never become a shortcut to Company02.
The application does not rely on a tenant ID supplied by the browser as the source of authority. Tenant context is determined from the authenticated user/session and used throughout the data-access layer.
Borrowers, loans, payments, reports and users belong to a tenant.
Subscriber and borrower uploads are associated with the correct company context.
Report exports inherit the same tenant and permission filters as on-screen views.
Subscriber branding remains separate from Platform Owner company information.
Limit what a user can do, not just what the menu shows.
Hiding a menu is not a sufficient access-control strategy. Backend authorization checks should continue to validate the authenticated user, tenant and permission before returning protected records or accepting a sensitive action.
- Platform Owner administration is separated from subscriber operations.
- Subscribers manage their own company users and branding.
- Collectors can document collection activity without rewriting loan balances.
- Historical financial corrections should use traceable adjustments or reversals.
Production checklist
Use HTTPS, strong database credentials, regular off-site backups, restricted file permissions, secure SMTP, scheduled vulnerability patching and periodic restore tests. External integrations should use secrets stored outside public web folders.