This guide is for operations, IT and product leads scoping a portal. It sits under our web application development service, which covers portals, admin tools and the integrations behind them.
In this guide
- What is the difference between a customer, partner and employee portal?
- What are the shared building blocks every portal needs?
- What does each portal type add on top?
- Which portal setup fits which situation?
- How do you turn the checklist into a build order?
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: other ways to get a portal
- When should you not build a custom portal?
- Limits of this guide
- Frequently asked questions
- Next step
What is the difference between a customer, partner and employee portal?
All three are logged-in web applications that give a group a private view of company data and actions they can take without emailing someone. The difference is who signs in, whose data they see and what the company is trying to remove from its inbox.
-
Customer portal
- Who signs in
- Buyers, account admins at client companies
- Main job
- Self-service orders, invoices, tickets and project status
- Typical data scope
- Only the records of the customer's own account
-
Partner portal
- Who signs in
- Resellers, agencies, suppliers, service partners
- Main job
- Deal registration, shared leads, materials, requests and payouts
- Typical data scope
- Records shared with that partner company, often by territory or programme
-
Employee portal
- Who signs in
- Staff and sometimes contractors
- Main job
- Documents, requests, approvals, onboarding and internal tools
- Typical data scope
- Records by department, role and employment status
When the first portal is built as a single-purpose site, the second one often becomes a separate build with its own user store and permission logic. Treating the shared parts as a platform avoids that.
What are the shared building blocks every portal needs?
Write this part once. Each row lists the questions a specification should answer before any screen is designed.
-
Identity and sign-in
Who creates accounts (self-registration, invitation, sync from a directory)? Is single sign-on needed for staff or for partner companies? When is multi-factor authentication required?
-
Roles and permissions
Which roles exist per portal type? Which actions does each role have? Can a client or partner admin manage their own users?
-
Data scoping
Which records belong to which company, territory or department? Is every query filtered by that scope on the server, not only in the interface?
-
Self-service actions
Which tasks move from email and phone into the portal (order, request, approve, upload, pay, book)? What is the approval chain for each?
-
Content and documents
Which documents, materials and knowledge base articles are shown, to whom, and who keeps them current?
-
Notifications
Which events send an email, an in-app message or a chat message, and can users choose?
-
Integrations and audit
Which systems hold the master data (CRM, ERP, HR, help desk)? What is synchronised, in which direction, and what is logged for audit?
Two rules keep the list honest. First, write permissions as actions on records ("an account admin can invite users to their own company"), not as page access. The OWASP Authorization Cheat Sheet recommends least privilege, denying by default and checking permissions on every request, which only works when permissions are written that way. Second, name the system of record for every data type; a portal that copies the CRM drifts out of date.
For sign-in, the NIST Digital Identity Guidelines (SP 800-63B) describe authenticator assurance levels, a useful way to decide which portal roles need multi-factor authentication. Where staff or partner companies already use an identity provider, OpenID Connect is the common standard for single sign-on to a web portal; our guide to portal sign-in and permission models compares the options.
What does each portal type add on top?
Each portal type adds a short list of its own. Anything that appears in two lists belongs in the shared blocks.
-
Customer portal
Company accounts with buyer and approver roles; order and quote history; invoice and document download; support tickets; project milestones where the relationship is a project
-
Partner portal
Partner company profiles and agreement status; deal or lead registration with conflict rules; shared materials with version control; partner-specific pricing or commission views; offboarding that removes access on the day a partnership ends
-
Employee portal
Directory and profiles; leave, expense and equipment requests; onboarding and offboarding checklists; internal policies and search across documents; links into HR and payroll systems
Our guide to B2B print portal requirements adds locked templates, budgets and approval chains for corporate print buyers on top of the same shared blocks.
Which portal setup fits which situation?
| Criterion | One platform, several portal types | Separate portal per audience | Off-the-shelf workspace with configuration |
|---|---|---|---|
| Best fit | Two or more portal types sharing customers, partners or data | One audience with very different rules or hosting needs | Standard needs such as projects, tickets and documents |
| Main strength | One user store, one permission model, shared integrations | Simple scope and independent releases | Fast start with no custom code to maintain |
| Main risk | A weak role model leaks data between audiences | Duplicate sign-in, duplicated integrations, drifting rules | Workflows bend to the product; limited data scoping |
| Choose it when | Roles and data scopes can be written as one matrix | Security or compliance rules require full isolation | No business rule is specific enough to justify a build |
Two decision rules help. If the same company can be a customer and a partner, choose one platform. If the portal's value is a standard workflow that a workspace product already does well, configure before you build.
How do you turn the checklist into a build order?
-
List the audiences and their top tasks
For each portal type, write the five tasks that remove the most email and phone work today.
-
Write the role and data scope matrix
One row per role, one column per action and record type, with the scope (own company, territory, department) in each cell.
-
Name the system of record for each data type
Decide what the portal stores, what it reads live and what it synchronises.
-
Specify identity
Choose registration, invitation or directory sync per audience, and set the multi-factor and single sign-on rules.
-
Build the shared blocks first
Sign-in, roles, scoping, notifications and audit logging go live before the first audience-specific screen.
-
Ship one portal type end to end
Start with the audience whose tasks are clearest and release to a small group.
-
Add the next portal type on the same platform
Reuse the role model and integrations; add only the rows from its own list.
Security checks belong in every step. The OWASP Application Security Verification Standard gives testable requirements for authentication, access control and session handling that can be copied into acceptance criteria, and WCAG 2.2 is the usual accessibility reference for forms, navigation and error messages.
Where AI fits
AI tools help most where portal users ask the same questions or upload the same documents: drafting answers from the knowledge base, routing requests to the right team and reading uploaded forms into fields. An engineer still checks that every AI feature respects the same role and data scope as the rest of the portal, because an assistant that can read every record will answer with data the user should not see. 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
Scoped portal assistant
A portal help assistant that answers only from records the signed-in role may read; not yet tied to a published case.
What delivery record exists, and what does not
Netbase has built logged-in platforms for several of the audiences in this checklist. 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, ticket creation, assignment and tracking, a knowledge base and a project platform with milestones. The Cloodo digital workplace, a Netbase Business Division, connects internal staff and outsourced specialists in one hybrid workspace with CRM, HRM, Cloud ERP and AI modules, and clients can follow their project's milestones and tasks in a shared Cloodo workspace.
Netbase's security practices include role-based access control and multi-factor authentication for admin dashboards. Netbase does not publish a portal adoption figure, a support ticket reduction or a timeline for a portal project; this guide explains a method, not a case study.
Alternatives: other ways to get a portal
- Configure an off-the-shelf workspace. Fits standard projects, tickets and documents with few custom rules. Cloodo, a Netbase brand, is an AI-powered digital workplace for managing services, launching projects and growing a company profile, and suits teams whose portal needs match that scope.
- Add a portal module to an existing CRM or ERP. Fits when every portal record already lives in that system and its permission model covers your audiences.
- Extend the website's CMS with member areas. Fits content-led portals with light actions; check the content model first, as our guide to content modelling before choosing a CMS explains, and compare options in headless CMS options compared.
- Build a custom portal platform. Fits when roles, data scopes or workflows are specific to your business, or when two portal types must share one platform.
Selection criteria: build when the role and data scope matrix cannot be expressed in the product you would configure, or when the same companies appear in more than one audience; configure when it can. Most Netbase projects are delivered on fixed-price contracts; milestone-based and monthly team retainer models are also offered, and a written checklist makes a fixed scope easier to agree.
When should you not build a custom portal?
Do not build when one audience needs a standard workflow a product already covers, when nobody will own content and user administration after launch, or when the source systems hold such poor data that the portal would only expose the errors. Fix the data and the ownership first.
Limits of this guide
- It covers requirements and build order, not visual design, hosting or framework choice.
- It does not compare named portal products.
Plan the next step with a Netbase consultant
Frequently asked questions
They can share one platform with separate portal types, as long as roles and data scopes are written as one matrix and checked on the server. Use fully separate portals only when security or compliance rules require isolation.
Usually not for small customers, who sign in with an account and multi-factor authentication. Single sign-on matters for staff and for large partner or client companies that want their own identity provider to control access.
The data scope. Documents list pages and roles but do not say which records each company, territory or department may see, and that gap is where data leaks between audiences.
Next step
If you are scoping a customer, partner or employee portal, send us your audiences and top tasks and we will reply with a proposal for a requirement 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.