Once customers or partners collaborate, versions multiply, approvals blur, and support calls pile up. A portal only works if roles and status are designed first — not bolted on later.
Have a customer portal built — with roles, not chaos.
Externals should only see and do what they may; your team still needs the full ops view. We build customer and partner portals as lean web apps: login, roles, files, status, next steps — planable for mid-market and B2B teams.
- Customer · partner portal
- Roles & rights
- For companies · scoped
Why email attachments and shared folders fail
B2B services, trades with project status, partner networks: recurring uploads, approvals, and follow-ups with the same pattern.
Not for you if…
- You want a full CRM/ERP replacement.
- Every customer has a totally different process.
- You expect unlimited self-service without an MVP cut.
- A public marketing site is the real goal (→ web design).
What a solid portal covers
Fewer features, more clarity. Typical MVP building blocks:
Access & roles
Customer, partner, internal — separate views, no accidental admin rights.
- Login / invite
- Role matrix
- Least privilege
Cases & status
Every case has a state: new, in review, approved, done.
- Queue
- Notifications
- History
Files & evidence
Uploads attach to the case — not scattered mailboxes.
- Upload rules
- Versions
- Approval context
Internal ops view
Team dashboard alongside the customer view — no double entry.
- Filters
- Assignment
- Export
Delivery via dashboard
Request, scope, milestones, and acceptance run in the customer dashboard — same model as all SHELL-AFFECT web apps.
Typically in scope
Portal with roles
Auth, views, cases, and UI for the agreed path.
Dashboard project ops
Transparent milestones and acceptance.
Security follow-on
CASP/review when identities and sensitive files matter.
Marketplace platform
No multi-vendor marketplace or unscoped feature pile.
Four steps to a portal MVP
Actors & rights
Who may see and trigger what — written in the briefing.
MVP cut
One core path live; nice-to-haves as phase 2.
Build & review
Reviews with real test users, not only mockups.
Acceptance & handover
Checklist, access, docs — your team runs it.
Access is security
Portals touch identities and often confidential files. We build with clear roles; reviews stay separate scopes — honest and optional.
- Roles and admin paths in scope
- No “enterprise secure” label without a review scope
- Link to the cyber security overview
Common questions
Customer portal or employee portal?
Same logic (roles + cases). Often we start with the external path; internal admin view ships in the same MVP or phase 2.
What does a portal cost?
Depends on scope — typically custom entry pricing. Orientation under Pricing; concrete band after dashboard briefing.
Do you also build the public company website?
Yes via web design — separate from the portal build so marketing and login surfaces stay clean.
Describe who should log in — and why.
Structured dashboard request: actors, rights, files, MVP cut.