Access your Back Office at your fingertips.
Download the app now on Google Play Store.
Scan the QR code
You can also scan QR code with your phone to download the app.
Understanding default roles on the Lendsqr admin console
Introduction
Picture this: you’ve just onboarded your team onto the Lendsqr admin console. Your loan officers need to process applications. Your compliance manager needs to review reports. But your CEO? She only needs to see the big picture, not accidentally approve a loan at 2 a.m.
So who gets access to what? That’s exactly what roles solve. Lendsqr gives you three default roles right out of the box: Super Admin, Admin, and Team. Each role comes with a specific set of permissions that matches what that person does in your lending operation. You don’t need to build anything from scratch; these roles already cover the most common access needs across a lending organization.
What are default roles?
Roles group permissions and assign them to people on your team. Instead of granting each user individual access to every feature manually, a role bundles related permissions under one label. Assign someone a role, and they instantly inherit everything it allows and nothing it doesn’t.
Default roles are the pre-built options Lendsqr provides to every lender automatically. You can’t edit them, but they cover the most critical access levels you need to get started.
The three default roles
Super Admin
The Super Admin is the root admin role on the Lendsqr admin console. This role unlocks unrestricted access to every capability on the platform. Super Admins manage users and permissions, adjust organization-wide settings, and make critical configuration changes.
Who should have this role: Assign this role to your founder, CTO, or whoever owns the overall setup and governance of your lending operation. Keep the number of Super Admins small; only people who genuinely need full platform control should have it.
Example: Your organization needs to restructure team permissions, configure a new loan product, and make a critical platform change. The Super Admin is the only role that can handle all of that without requesting additional access.
Admin
Admins get broad access to most areas of the admin console. They manage users and teams and adjust certain settings. However, they can’t make critical or organization-level changes that are reserved for the Super Admin.
Who should have this role: Operations managers, credit managers, and senior team leads are the right fit. These are the people who run day-to-day lending activities. They need enough control to keep things moving, but they don’t need to touch core platform configurations.
Example: An operations manager onboards a new loan officer, updates team assignments, and adjusts workflow settings all within the Admin role. They get the access they need without the risk of triggering a critical platform-level change.
Team
The Team role is the default for ordinary team members. Users in this role handle their core daily functions on the platform. They can’t create users, add loan products, or make system-level changes.
Who should have this role: Loan officers, customer support agents, and field staff all belong here. These are task-focused team members who don’t need administrative access. They get what they need to do their job, nothing more.
Example: A loan officer reviews and processes incoming applications entirely within the Team role. They don’t need product configurations or user management access, just the tools to action their work.
Assigning the right role to each team member isn’t just about convenience. It’s a security and compliance decision. Giving someone more access than they need increases the risk of accidental changes, unauthorized actions, or data exposure. Keeping roles tightly matched to job functions ensures your data stays protected.
For lenders operating in regulated environments, whether in Nigeria, Kenya, India, or elsewhere, maintaining clear role definitions also supports internal governance requirements and makes it easier to demonstrate accountability if ever questioned by a regulator.
Learn more
To understand how to design a team structure that supports responsible lending, visit the Lendsqr blog: https://blog.lendsqr.com for practical guides on lending operations and credit risk management.
