This guide is for IT leads, CTOs and operations managers whose company runs several internal applications, such as an ERP, an admin panel, a reporting tool or a custom workflow system, and who can no longer say who may approve, export or delete what. For sign-in options for customer and partner portals, see our guide to portal authentication and permission models. For a review of an existing application's access control, see application security assurance.
In this guide
- Why do internal apps need role design, not only single sign-on?
- Which role design pattern fits which problem?
- What goes in a role catalogue?
- How do you roll out SSO, MFA and least privilege?
- Where should MFA and step-up checks sit?
- When should you not add more access machinery?
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: who designs and runs internal access, and how to choose
- Limits of this guide
- Frequently asked questions
- Next step
Why do internal apps need role design, not only single sign-on?
Single sign-on answers who the user is; it does not decide what that user may do inside each application. A company can connect every internal app to one identity provider and still leave a finance clerk able to approve their own payment, because the application gives every signed-in employee the same broad role. Least privilege is enforced inside the application, through its roles and data scope.
The OWASP Authorization Cheat Sheet sets the baseline every pattern below assumes: deny by default, grant the least privilege a task needs and check permissions on the server for every request. Broken access control is the first category of the OWASP Top 10 2025, which is why role design is a security decision and not only an administration task.
Internal apps differ from customer portals because users change jobs, and most access problems come from permissions that were correct once and never removed.
Which role design pattern fits which problem?
Six patterns cover most internal applications. They combine: job roles with data scope are the base, and the others are added where a specific risk appears.
| Pattern | What it solves | How it fails | Use it when |
|---|---|---|---|
| Job roles with data scope | Clear, reviewable access: a role defines actions, a scope (own team, own branch, all) defines records | One new role per exception until nobody can review the list | Always, as the base layer |
| Composable permission sets | Shared duties without duplicate roles: a user holds a job role plus a small set such as "can export" | Sets stacked on one person add up to admin rights | Several roles share one sensitive duty |
| Group-to-role mapping from the identity provider | Joiners and leavers handled in one place; the app reads groups at sign-in | Undocumented mappings; a group renamed in the provider silently grants or removes access | More than a few apps share the same workforce |
| Separation-of-duties pairs | Prevents one person from both creating and approving, or both changing and releasing | Pairs enforced only in policy documents, not in code | Payments, refunds, price changes, user management |
| Time-limited elevation | No standing admin rights; admin access is requested, approved and expires | Approvals rubber-stamped, or expiry not enforced | Any role that can change configuration, permissions or bulk data |
| Break-glass accounts | Emergency access when the identity provider or MFA service fails | Shared passwords nobody rotates, use never alerted | Every company that depends on single sign-on for all apps |
NIST SP 800-53 describes the underlying controls as account management, separation of duties and least privilege, and the NIST role-based access control project covers role hierarchies and constrained roles in depth. For emergency access, Microsoft's guidance on emergency access accounts recommends two or more such accounts with phishing-resistant authentication, excluded from sign-in policies that could block them, and an alert on every use.
What goes in a role catalogue?
A role catalogue is a one-page table the business, not only IT, can read and sign off, with one row per role per application.
-
Role
Business name, for example "Accounts payable clerk", never a person's name
-
Owner
The manager who approves membership and confirms it at each review
-
Permissions
Actions on record types: view, create, edit, approve, export, delete
-
Data scope
Own records, own team, own branch or company-wide
-
Sign-in and MFA
Single sign-on group, MFA required, and step-up for which actions
-
Conflicting roles
Roles the same person must not hold at the same time
-
Elevation
Whether admin actions need a time-limited grant, and who approves it
-
Review cadence
How often the owner confirms the members
Keep it short: a role that exists for one person is an exception and belongs in the elevation process.
How do you roll out SSO, MFA and least privilege?
-
Inventory accounts
List every internal app, its local accounts, shared accounts, service accounts and the people with admin rights today.
-
Connect sign-in to one identity provider
Use OpenID Connect or SAML for each app, then disable local passwords except the break-glass accounts.
-
Write the role catalogue
Start from real jobs, assign an owner per role and mark the conflicting pairs.
-
Map groups to roles in code
Keep the mapping in version control so a change is reviewed like any other change, and enforce the role and data scope on the server.
-
Set MFA and step-up
Require MFA at the provider for everyone, and a fresh check before high-risk actions.
-
Remove standing admin rights
Replace them with time-limited elevation and log every grant.
-
Automate joiners, movers and leavers
Provision from the HR record or the provider, for example with SCIM, and treat a move between departments as remove-then-add, not add-only.
-
Review on a schedule
Owners confirm members, unused roles are deleted and every permission change stays in the audit log.
Where should MFA and step-up checks sit?
MFA belongs at the identity provider, so every internal app inherits the same policy and nobody maintains a second-factor setup per application. The NIST Digital Identity Guidelines (SP 800-63B) treat SMS and voice codes as a restricted authenticator and require a phishing-resistant authenticator at the highest assurance level, which is the right target for administrators.
Step-up checks belong in the application, because only the application knows which action is risky. Ask for a fresh authentication before approving a payment, exporting a customer list, changing another user's role or deleting records in bulk.
When should you not add more access machinery?
Do not add a policy engine or a just-in-time access product for a handful of users and two applications; a written role catalogue, MFA at the provider and a quarterly review cover that size. Do not create one role per person to mirror an old permission list; that keeps the problem and only renames it. Do not rely on single sign-on alone, because a stolen session or an over-broad default role still opens every application connected to it.
Where AI fits
AI helps around access design, not inside the access decision. A model can compare role members against their peers and flag outliers before a review, summarise a role catalogue for an owner who must sign it off and draft negative test cases for each separation-of-duties pair. Engineers and role owners still decide every grant, and any AI assistant inside an internal app must query data with the signed-in user's own role and scope, never through an account that can read everything. Netbase works with the major commercial and open-source AI tools and models, chosen per project, under human control.
- In delivered work
Recommendation engine
A recommendation engine delivered for 4over4's online store suggests products from browsing history and previous purchases.
- In delivered work
Knowledge assistants and document AI
Retrieval-augmented knowledge assistants and document AI delivered for clients that are not named.
- Available capability
Access review assistant
An assistant that prepares role member lists and outliers for owners to confirm; not yet tied to a published case.
What delivery record exists, and what does not
Netbase's published security practices include role-based access control and MFA for admin dashboards, secure code review and version control, TLS in transit and AES at rest, vulnerability scanning and penetration testing, and disaster recovery. Security by design is part of how Netbase approaches delivery.
Netbase works as offshore development partner on a multi-tenant cloud ERP for a US client whose modules include HR management, custom fields and workflows, and work and project management, the kind of internal system where roles and approvals decide who sees what. For business partners, Netbase also deploys a help desk and B2B CRM with ticket creation, assignment and tracking.
Netbase holds ISO 27001 certification and a SOC 2 Type II attestation for its own operations; neither certifies a client's application or its access model. Delivery follows a six-step lifecycle with weekly reviews, which is where a role catalogue and its open exceptions are reviewed. Netbase does not publish access-review results, account-takeover figures or a timeline for an access redesign; this guide explains a method, not a case study.
Alternatives: who designs and runs internal access, and how to choose
- Use the role features of each application. Fits a few off-the-shelf tools with built-in roles; the role catalogue still applies, written per tool.
- Use your identity provider's governance features. Fits companies with many applications and an IT team that runs provisioning and access reviews centrally.
- Build role and scope checks into custom applications. Fits internal systems with approvals and data scopes that off-the-shelf roles cannot express; see the secure development lifecycle for where to test them.
- Commission an access review. Fits when you need an outside view of an existing application; the OWASP Top 10 code review checklist shows what reviewers look for.
Selection criteria: choose by how many applications share the workforce, whether approvals and data scopes are built into custom code, who will own reviews after go-live and how often people change jobs. Most Netbase projects are delivered on fixed-price contracts, and a signed role catalogue makes that scope easier to agree.
Limits of this guide
- It does not compare named identity, governance or privileged access products.
- It covers workforce access to internal applications, not customer sign-in, API-to-API authentication or machine keys and secrets.
Plan the next step with a Netbase consultant
Frequently asked questions
No. Single sign-on confirms who the user is, but each application must still decide what that user may do and which records they may see. Without roles, data scope and server-side checks, one compromised account can reach everything the default role allows.
As few as the real jobs require, each with an owner and a data scope. When two roles differ by one permission, use one role plus a small permission set, and handle one-off needs through time-limited elevation instead of new roles.
No. Administrators should request admin rights for a task, have the grant approved and let it expire automatically, with every grant logged. Keep two monitored break-glass accounts for the case where the identity provider or MFA service is unavailable.
Next step
If your internal apps have grown roles nobody can explain, send us the list of applications and admin accounts and we will reply with a proposal for a role catalogue workshop and a build order.
Related services and solutions
Application security assurance for web, SaaS and AI features Netbase provides application security testing for product and engineering leaders to find and fix vulnerabilities before release, including in AI features. We review code with AI-assisted triage, scan dependencies and test running applications, then rank findings and retest fixes. Netbase's own alignment with ISO 27001 and SOC 2 Type II covers Netbase's operations, never your application.
Learn More
Web application development with AI built in where it converts Netbase provides web application development for product and commerce teams that need fast, maintainable web apps and storefront front ends, with AI search, assistants and automation added where they measurably help. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to its published case studies, PrintLeo's page load improved 35% and 4over4's conversion rose 48%.
Learn More
Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system A custom cloud ERP from Netbase is one browser-based system where a growing company runs its projects, finance, HR and customer relationships on shared data, with AI that reads invoices and forecasts demand and cash. It suits SMEs that have outgrown spreadsheets but not their own way of working, on the foundation of Cloodo Workspace, which Netbase built and runs.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.