This guide is for the product, IT or operations lead who is scoping a customer, partner or employee portal and has to answer "can our clients sign in with their own accounts?" before the build. It complements our portal requirements checklist and the web application development service, where Netbase builds portals and admin tools.
In this guide
- Why treat sign-in, MFA and permissions as three decisions?
- Which sign-in method fits each portal audience?
- What MFA method should each role use?
- Which permission model fits your portal?
- How do you choose and build the model?
- When should you not add SSO or a policy engine yet?
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: how else can a portal get sign-in and roles?
- What does this guide leave out?
- Frequently asked questions
- Next step
Why treat sign-in, MFA and permissions as three decisions?
Authentication answers "who is this user?" and authorization answers "what may this user do with this record?". A portal can pass the first and fail the second: a partner who signs in correctly with single sign-on can still see another partner's orders if the permission check only looks at the role and not at the company. Treating sign-in, multi-factor strength and the permission model as three decisions keeps each one testable on its own.
The OWASP Authorization Cheat Sheet sets the baseline for the third decision: deny by default, apply least privilege and check permissions on every request on the server, not only in the menu the user sees.
Which sign-in method fits each portal audience?
Different audiences bring different identity sources. Customers usually have no identity provider you can use; employees almost always do; partner and large client companies sit in between and often ask for single sign-on once the portal matters to them. Employee-only apps follow the role patterns for internal apps.
-
Small customers
- Usual sign-in
- Portal account with email verification, or social sign-in
- MFA expectation
- Optional or risk-based; required for payment and personal data changes
- Who administers users
- The customer, through self-service
-
Large client or partner companies
- Usual sign-in
- Single sign-on with the company's own identity provider
- MFA expectation
- Enforced by the company's provider
- Who administers users
- A client or partner admin inside the portal, or the provider through provisioning
-
Employees and contractors
- Usual sign-in
- Single sign-on with your workforce identity provider
- MFA expectation
- Always on
- Who administers users
- Your IT team, with offboarding from the provider
-
Portal administrators
- Usual sign-in
- Single sign-on or a local account
- MFA expectation
- Always on, phishing-resistant where possible
- Who administers users
- A small named group, reviewed regularly
Two protocols cover almost every single sign-on request. OpenID Connect is an identity layer on top of OAuth 2.0 and suits modern web and mobile front ends. SAML 2.0, published by OASIS, is older and XML-based, and many large companies still use it for workforce sign-in. A portal that serves large clients usually needs to accept both, which is a reason to put sign-in behind one identity service instead of wiring each protocol into the application.
What MFA method should each role use?
Multi-factor authentication methods differ in how well they resist phishing. The NIST Digital Identity Guidelines (SP 800-63B) define authenticator assurance levels, treat one-time codes sent by SMS or voice as a restricted authenticator, and require a phishing-resistant authenticator at the highest level. Passkeys, built on the W3C Web Authentication standard and promoted by the FIDO Alliance, are phishing-resistant because the credential is bound to the site's domain.
A practical rule for portals: require MFA for every administrator and for any role that can export data, approve payments or manage other users; prefer passkeys or an authenticator app over SMS for those roles; offer, but do not force, MFA to small customers unless the portal holds sensitive personal or financial data. The OWASP Multifactor Authentication Cheat Sheet adds the recovery side: plan how a user who loses a device regains access without a support agent becoming the weak point.
Which permission model fits your portal?
Role-based access control (RBAC) attaches permissions to roles. Attribute-based access control (ABAC) decides each request from attributes of the user, the record and the context. Relationship-based access control (ReBAC) decides from the links between users and records, the approach described in Google's Zanzibar paper.
| Criterion | RBAC (roles) | ABAC (attributes) | ReBAC (relationships) |
|---|---|---|---|
| What it expresses well | Job-shaped permissions: buyer, approver, admin | Context: department, region, record status, device, MFA used | Ownership and sharing: this user belongs to this company, which owns this order |
| Audit effort | Low: list roles and their permissions | High: every policy must be read and tested | Medium: inspect the relationship graph per record |
| Typical failure | Role explosion, one role per exception | Policies nobody can explain after a year | A wrong or stale relationship opens a whole branch of records |
| Portal it fits | One audience, few roles, simple data scope | Employee portals with regional or status rules | Multi-company customer and partner portals, shared documents |
The NIST role-based access control project describes the RBAC model in depth, and NIST SP 800-162 gives the reference guide to ABAC. In practice most business portals combine them: roles define what actions exist, and a company or ownership check on every query defines which records those actions apply to. That combination is often enough; a dedicated policy engine pays off only when rules change faster than releases.
How do you choose and build the model?
-
Map the audiences
List every audience, the company or unit each user belongs to and the identity provider each one already has.
-
Write the role and scope matrix
One row per role, one column per action and record type, with the scope (own records, own company, region, everything) in each cell.
-
Pick sign-in per audience
Portal accounts for small customers, single sign-on by OpenID Connect or SAML for companies and staff, behind one identity service.
-
Set MFA by role, not by audience
Administrators and roles that export, approve or manage users get phishing-resistant MFA; others get it as an option or by risk.
-
Enforce on the server
Every API call checks the role and the data scope; hiding a button is never the control.
-
Plan provisioning and offboarding
Decide whether client admins invite users or the client's provider provisions them, for example through the SCIM standard, and test that removed users lose access.
-
Review access on a schedule
Export the role and scope assignments, have owners confirm them and log every permission change.
When should you not add SSO or a policy engine yet?
Do not build single sign-on for an audience of small customers who have no identity provider; email verification and optional MFA serve them better. Do not introduce ABAC or a separate policy engine while the role and scope matrix still fits on one page; it adds a language, a service and a test burden before there is a rule that needs it. SMS codes remain acceptable as an option for low-risk customer accounts when the alternative is no second factor at all.
Where AI fits
AI helps around the permission model rather than inside it: summarising an exported role and scope matrix for an access review, flagging users whose permissions differ from their peers and drafting test cases for each role. An engineer still decides every permission, and any AI assistant inside the portal must query data with the signed-in user's own scope, never with a service 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
Permission-aware portal assistant
A portal assistant that answers only from records the signed-in role and company may read; not yet tied to a published case.
What delivery record exists, and what does not
For a Dubai-based loyalty and rewards technology company that is not named, Netbase delivered a headless multi-store reward shop platform with individually branded reward shops per client programme, single sign-on, integrations with the client's points middleware and ordering service, and a centralised super-admin dashboard. For business partners, Netbase deploys a help desk and B2B CRM with sales chats and client requests in one dashboard and ticket creation, assignment and tracking.
Netbase's own security practices include role-based access control and multi-factor authentication for admin dashboards, and Netbase holds ISO 27001 certification and a SOC 2 Type II attestation for its own operations; neither certifies a client's portal. Netbase does not publish an account-takeover figure, a sign-in conversion rate or a timeline for an authentication project; this guide explains a method, not a case study.
Alternatives: how else can a portal get sign-in and roles?
- Use the identity features of your framework or CMS. Fits one audience with a few roles and no single sign-on request; check member roles against your content model first.
- Use a hosted identity service. Fits when several audiences, both SSO protocols and passkeys are needed; the portal keeps its own role and scope checks.
- Run your own identity server. Fits when data residency or contract terms rule out a hosted service and a team can operate it.
- Add a dedicated authorization service. Fits multi-company portals with sharing rules that change often.
Selection criteria: choose by the number of audiences, whether any client has asked for SSO, how often permission rules change and who will run the identity layer after launch. Most Netbase projects are delivered on fixed-price contracts, and a written role and scope matrix makes that scope easier to agree. Our SaaS security checklist covers the controls around the model.
What does this guide leave out?
- It does not compare named identity or authorization products.
- It covers web portals, not API-to-API authentication or machine identities.
Plan the next step with a Netbase consultant
Frequently asked questions
Not for small customers, who sign in with a portal account and optional multi-factor authentication. Single sign-on becomes necessary when large client or partner companies want their own identity provider to control who can access the portal.
Roles alone are not enough, because a role says what a user may do but not whose records. Add a company or ownership check on every query, or a relationship model when records are shared between companies.
For low-risk customer accounts SMS codes are better than no second factor. For administrators and roles that export data or approve payments, require passkeys or an authenticator app, which resist phishing better.
Next step
If you are scoping a portal, send us your audiences and roles and we will reply with a proposal for a role and scope workshop and a build order.
Related services and solutions
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
AI-ready SaaS development from a team that runs its own SaaS Netbase provides SaaS development for founders and product teams to launch and scale multi-tenant subscription software with AI features customers will pay for. We build and operate our own SaaS platforms, Printcart and the AI-powered Cloodo workplace, and bring that experience to client products. Discovery fixes the MVP scope and schedule.
Learn More
Project collaboration workspace with AI: plans, tasks, files and clients on one project record A project collaboration workspace from Netbase is software where teams, freelancers and clients plan work, assign tasks, share files, log time and discuss decisions on one project record, linked to sales, billing and HR. We design and build it custom, drawing on Cloodo, our own digital workplace, and add AI that summarises and flags while managers decide.
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.