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
You have just onboarded your team onto the Lendsqr admin console. The loan officers need to process applications. Your compliance manager needs to review reports. Your CEO only needs to see the big picture, not accidentally approve a loan at 2 a.m.
So who gets access to what? That is 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 match what that person does in your lending operation. You do not need to build anything from scratch. These roles already cover the most common access needs across a lending organization.
What are default roles?
A role is a bundle of permissions assigned to a person on your team. Instead of granting each user individual access to every feature manually, a role groups related permissions under one label. Assign someone a role and they instantly inherit everything it allows, and nothing it does not.
Default roles are the pre-built options Lendsqr provides to every lender automatically. You cannot edit them, but they cover the most critical access levels you need to get started. Think of them as your access control foundation. Everything else builds on top of them.
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 organisation-wide settings, and make critical configuration changes.
Who should have this role: Assign it 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.
Real-world example: A fintech lender is setting up on Lendsqr for the first time. The CTO needs to configure loan products, set up the decision engine, and invite the rest of the team. Only the Super Admin role gives them access to do all of this without needing to request permissions at every step.
Admin
Admins get broad access to most areas of the admin console. They manage users and teams and adjust certain settings. However, they cannot make critical or organization-level changes. Those 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 without touching core platform configurations.
Real-world example: A microfinance lender’s operations manager needs to onboard three new loan officers, update team assignments, and adjust workflow settings before Monday. All of this falls within the Admin role. They get the access they need without the risk of triggering a platform-level change that could affect the entire organization.
The Team role is the default for ordinary team members. Users in this role handle their core daily functions on the platform. They cannot create users, add loan products, or make system-level changes.
Team
Who should have this role: Loan officers, customer support agents, and field staff all belong here. These are task-focused team members who do not need administrative access. They get what they need to do their job, nothing more.
Real-world example: A loan officer at a digital lending company reviews and processes 30 incoming applications every day. They need access to borrower profiles and loan request queues. They do not need access to product configurations, pricing settings, or user management. The Team role gives them exactly what they need and keeps everything else protected.
Why getting roles right matters
Assigning the right role to each team member is not just about convenience. It is a security and compliance decision.
Giving someone more access than they need increases the risk of accidental changes, unauthorized actions, or data exposure. A loan officer who can edit loan products is a liability. A customer support agent who can delete users is a risk. Keeping roles tightly matched to job functions ensures your platform stays protected and your data stays clean.
For lenders operating in regulated environments, whether in Nigeria, Kenya, Ghana, South Africa, or elsewhere, maintaining clear role definitions also supports your internal governance requirements. If a regulator ever asks you to demonstrate who had access to what and when, your role configuration is your first line of evidence.
How Lendsqr makes role management simple
On the Lendsqr admin console, roles are assigned at the point of invitation. When you invite a new team member, you select their role before sending the invite. The moment they accept and create their account, they land on the platform with exactly the access their role allows.
You can also update a team member’s role at any time from the Team Members section of your organizational settings. Role changes take effect immediately. There is no waiting period and no need to re-invite the team member.
This makes it easy to promote a loan officer to an operations manager role, restrict access when a team member changes responsibilities, or add a new Super Admin when your leadership team grows.
Can you go beyond the default roles?
Yes. The three default roles cover the most common access patterns in a lending operation. However, some organizations need more precision. A lender with a large team may want a role that allows loan approval but not user management. Another may want a role that allows report viewing but not transaction access.
Lendsqr allows you to create custom roles with specific permission combinations that go beyond what the three defaults offer. Each custom role can be tailored to a specific function within your organization and assigned to the relevant team members. To get started, see: How to create custom roles and permissions for your lending team.
Troubleshooting
A team member cannot access a feature they need. Check their assigned role and confirm that the feature falls within that role’s permissions. If not, consider whether upgrading their role or creating a custom role is the right solution.
Too many people have Super Admin access. Review your team member list and downgrade users who do not need unrestricted access. Limit Super Admin to two or three people at most, the people who genuinely own platform governance.
A team member’s role does not match their job function anymore. Update their role from the Team Members section in organizational settings. Changes take effect immediately without needing to re-invite the team member.
Frequently asked questions
Can I edit the default roles? No. The three default roles have fixed permissions that cannot be changed. If the default options do not fully match your team structure, create a custom role with the exact permissions you need.
How many Super Admins can I have? There is no hard limit. However, best practice is to keep the number as low as possible. Fewer Super Admins means less risk of accidental platform-wide changes.
What happens if I assign the wrong role to a team member? You can update a team member’s role at any time from the Team Members section. Changes apply immediately.
Do roles apply across all loan products? Yes. Roles on the Lendsqr admin console apply platform-wide unless access is further restricted at the product or branch level.
Can a team member have more than one role? Each team member is assigned one role at a time. To adjust what they can access, update their role or create a custom role that combines the permissions they need.
