One Home For Every Public Portal You Run
Every public portal you run — customer, candidate, kiosk — listed in one catalog, with identity and recovery, branding, audit logs, and analytics handled once instead of per portal.
See Portals In Action
Manage every public-facing portal across your apps from one place — a cross-app catalog with live preview and on/off control, a shared OTP and magic-link recovery layer with a searchable audit log, and cross-portal traffic analytics.
What Portals Helps You Do
Six cross-cutting capabilities that every public portal needs but no single app should reimplement.
See Every Portal In One Catalog
A unified catalog lists every portal — owning app, status, public URL and an "open preview" link — and opens or closes each one. The owning app decides what is in it.
Configure Identity & Recovery Once
One home for the OTP / magic-link recovery rate limit, the abuse-alert threshold and audit retention — applied uniformly to every portal on the shared layer.
Search The Audit Log
Browse the recovery audit log across every portal — filter by portal, event, identifier hash, or IP. CSV export for audit and security reviews.
Track Cross-Portal Analytics
Visit counts, recovery requests and send success rate across the public portals in one dashboard. Per-portal drill-downs included.
Apply Branding And Custom Domains
Your workspace's logo, colors and fonts apply to every portal. Your public job board can live on a hostname you own, with its HTTPS certificate issued for you.
Surface Security Signals
Anomaly detection on the recovery layer — failed delivery spikes, top offending IPs, identifiers with the most flagged events. A spike alerts your Portals admins.
An Umbrella That Doesn't Take Over
Portals manages cross-cutting concerns without owning what each portal shows. The Catalog decides whether a portal is open; the owning app decides what is in it.
Each Owning App Keeps Its Portal
Field Service owns its Customer Portal. Recruiting owns its Candidate Portal. Offboarding owns the Former Employee Portal. eSig owns the kiosk. Drive owns public links. Portals doesn't move any of that — it catalogs every portal and gives you one switch to open or close each one.
- Field Service Customer Portal — work-order status, technician ETAs, customer payments.
- Recruiting Candidate Portal — application status, interview scheduling, offer letters.
- Offboarding Former Employee Portal — pay stubs, tax forms, HR documents and experience letters.
- AFO Visitor Surface — public booking widget for inbound service customers.
- E-Signature Kiosk — public-link signing flow for documents.
- Drive Public Links — share-with-anyone links for files and folders.
Identity & Recovery, Centralized
The OTP / magic-link recovery layer lives in the shared identity & recovery layer — a shared concern every portal opts into. Configure the rate limit, the abuse alert and retention once, applied everywhere.
- Magic link or OTP code — fixed by each portal's owning app.
- Rate-limit window + max — protect against enumeration and brute-force attacks.
- Hashed identifiers — emails and phone numbers are stored only as one-way hashes in the audit log.
- Audit retention — configurable retention window (default 180 days).
- Per-portal opt-in — owning apps choose to use the shared recovery layer or roll their own.
Audit, Search, And Hand Off
The audit log is a structured browser over the recovery audit log — filter by portal, event type, identifier hash, IP — with CSV export for security and compliance.
- Cross-portal search — one query across every portal's recovery history.
- Filters that compose — portal + event + time window + IP, all at once.
- CSV export — for audit packets and security reviews.
- Anomaly evidence — the Portals Agent gathers it in the chat for handoff.
- Owner handoff — the umbrella never blocks an IP or revokes a token; it routes the question to the owning app.
Portals That Compose Through The Umbrella
Each portal stays owned by its app — Portals catalogs, configures recovery, and audits them.
→ Field Service Customer Portal
Customers track work orders, technician ETAs, and payment status. The portal feature ships with Field Service; the umbrella surfaces it in the catalog.
→ Recruiting Candidate Portal
Candidates check application status, accept interview slots, and sign offer letters. Recruiting owns the feature; Portals catalogs it.
→ Offboarding Former Employee Portal
Former employees sign in with a one-time access token sent to their email or phone to retrieve pay stubs, tax forms, HR documents and experience letters.
→ AI Front Office Public Widget
The public booking widget on {slug}-book.workforce.mangoapps.com for inbound customer chat, SMS, and voice.
→ E-Signature Kiosk
Public-link signing flow for external signers. Lives in E-Signature; surfaces in the Portals catalog.
→ Drive Public Links
Anyone-with-link shares for files and folders. Drive owns the feature; Portals' audit log captures every recovery event.
Portals In Practice
A practical scope check: what the app covers, which controls matter, and the workflows teams usually run first.
Core workflow
See every public-facing portal in your business in one catalog — status, owning app, public URL, and a one-click preview.
Controls that matter
Audit Log includes a recovery event browser with date / portal / event filters and IP and user-agent capture per request.
Scope and specs
Useful specs: Default rate-limit window: 60 minutes (configurable); Default limit: 3 recovery attempts per window per identifier (configurable); Default audit retention: 180 days (configurable).
See every portal at a glance
See which public surfaces are live — Field Service Customer Portal, Candidate Portal, Former Employee Portal, AFO visitor surface, eSig kiosk, public Drive links, and more. Each row shows owning app, status, and a preview link.
Tune recovery security in one place
A spike in failed OTP attempts? Drop the rate-limit max from 5 to 3 in Identity & Recovery — every portal using the shared recovery layer picks up the new limit on the next request.
Investigate a recovery anomaly
A user reports they never got their portal token. Filter the audit log by their identifier-hash (or IP), see whether the request was rate-limited, dispatched, or actually consumed, and trace the failure mode without exposing plaintext PII.
REPLACES POINT TOOLS
One portal umbrella in place of five disconnected external surfaces
Most companies bolt together Salesforce Experience Cloud for customers, a Webflow microsite for candidates, a SharePoint extranet for partners, and a HubSpot CMS portal for documentation — each with its own identity, audit, and recovery story. Portals catalogs them all under one governance surface without owning per-portal features.
Salesforce Experience Cloud
Per-user-priced customer / partner community
- No per-external-user license — customers, candidates, and former employees access portals freely
- Owning app keeps its own data model — Portals doesn't force a Salesforce-shaped schema
- One audit + recovery surface across every external portal, not one per community
HubSpot CMS portals
Customer / knowledge portals built on the HubSpot CMS
- Portals lives next to the actual workforce stack — not a marketing CMS retrofitted for ops
- Recovery flows (token rotation, identifier-hash) work the same across every portal type
- No separate marketing-team-owned surface for a CS / Field Service portal
SoftLanding / extranet point tools
External-stakeholder portal SaaS
- One umbrella across customer, candidate, former-employee, signing, and file-sharing portals
- Catalogs and governs portals the platform's own apps own — not a parallel surface
- Same per-employee pricing as the rest of MangoApps, no per-external-user creep
Custom Webflow / Next.js builds
DIY public sites and portals
- No engineering team required to spin up the portal — the owning app already ships it
- Cataloged, audited, and recovery-ready by default — not a custom build that drifted
- Portals' umbrella adds DNS, SSL, and rate limiting without devops on speed-dial
SharePoint extranet
Microsoft-only external portal
- Works for external users who don't have (and shouldn't get) Microsoft licenses
- One recovery audit log across every external portal — not a SharePoint-shaped subset
- Custom subdomains, brand control, and recovery built in — not a SharePoint theme hack
PLATFORM ADVANTAGE
Portals inherits everything else MangoApps already does
A standalone portal tool has to build, buy, or integrate each of these. Portals gets them for free because the platform already runs them.
Identity & SSO
Authenticated portals reuse SAML/OIDC SSO; anonymous portals get identifier-hash + rate limiting. One identity story across every surface.
DNS & SSL automation
Custom subdomains, automated cert provisioning, and renewal handled by the umbrella — never a per-portal devops project.
Recovery audit log
Every portal recovery event lands in the Portals recovery audit log, kept for the retention window you set (default 180 days).
Rate limiting & abuse
Token rotation, identifier-hashing, and abuse throttling handled at the umbrella — not re-invented per portal.
Branding & theme
One brand kit — logo, palette, type — applied across every external portal. Updates ripple in one click.
Workflow & automation
A portal action can trigger a Task, a workflow, a notification, or a Bot — using the same automation engine as every other app.
INDUSTRY FIT
Built for the organizations where every external relationship gets a portal
Portals is the umbrella for companies that already run three or four public-facing surfaces — and need one place to catalog, govern, and recover them.
Field Service & Trades
Customer portal for work-order tracking, technician portal for job cards, and partner portal for subcontractors — all under one umbrella.
Staffing & Recruiting
Candidate portal for application status and offer acceptance, plus former-employee portal for tax docs and COBRA — same governance surface.
Financial Services
Client portal for statements + signatures, advisor portal for compliance docs — portal recovery events recorded in an audit log with a retention window you set.
Healthcare
Patient intake widget, referring-physician portal, and vendor portal with HIPAA-aware audit and break-glass recovery.
Professional Services
Client portal for engagement deliverables, alumni portal for former staff, partner portal for referral firms — one umbrella, one audit.
Manufacturing & Distribution
Supplier portal for POs, distributor portal for marketing assets, and customer portal for warranty claims — cataloged in one place.
WHY MANGOAPPS WINS
One platform beats a stack of point solutions on every axis
The argument finance, security, IT, and the portal owners all share — and the one a per-portal SaaS vendor structurally cannot answer.
Cheaper than the stack
One per-employee suite license — no per-external-user fees, no per-portal SaaS subscriptions, no per-community Salesforce add-on.
More secure
One identity perimeter, one recovery audit log, one recovery playbook across every external portal. Nothing for security to re-certify per surface.
Easier to deploy
A new portal goes live the day the owning app turns it on — Portals catalogs, brands, and audits it without devops on speed-dial.
Easier to use
External users get a single branded surface; admins get a single catalog. No "which vendor owns this portal?" lookup.
Easier to manage
Catalog, recovery, abuse throttling, and audit live in one umbrella — owning apps keep their own data and features.
Easier to extend
A new app that needs a public portal inherits DNS, SSL, audit, and recovery — without re-implementing the umbrella per app.
AI is actually better
One Portals agent — daily-ops checks and audit-grade evidence — reads across every portal in the catalog, under the same permission model.
Pair Portals With Its Agent
One read-only Portals Agent answers daily-ops checks and assembles audit-grade evidence; remediation stays in the owning app's admin UI.
Portals AI
Posture snapshots, anomaly evidence, audit log drill-downs across every public portal.
Customer Success
How Teams Run Public Portals
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
There’s an absolute return on investment with MangoApps as our partner. We’ve been able to actualize our vision to make community participation and employee engagement happen.
Dr. Kevin Klauer
Chief Medical Officer
Team Health
Frequently Asked Questions
No. Each owning app keeps its portal — Field Service owns the Customer Portal, Recruiting owns the Candidate Portal, and so on. Portals is the umbrella for cross-cutting concerns: catalog, identity & recovery, audit log, branding, custom domains, analytics. The owning app decides what its portal shows; the Catalog is where an admin opens or closes it to the public.
Identity & Recovery is the shared OTP / magic-link layer for portals that need anonymous identity verification — usually for a customer or candidate who doesn't have a MangoApps login. Owning apps opt in to the shared Identity & Recovery layer. When they do, the recovery rate limit, the abuse-alert threshold and audit retention are configured here, applied everywhere.
Your public job board can — add a hostname such as careers.yourcompany.com, then add the two DNS records it shows — one proves the domain is yours, one points it at us. Its HTTPS certificate is issued and renewed for you, and the domain turns on by itself. A main domain sends visitors to your OneMango sign-in page. Other portals cannot have a hostname of their own yet.
Every recovery event — request, send, no match, consume, fail, rate-limit, invalid link or code — writes to the recovery audit log, scoped to the portal and the owning app. The Audit Log surface lets admins search across every portal by event, identifier hash, IP, and time window. CSV export for compliance and security reviews.
Cross-portal visit counts, recovery requests, success rate, top offending IPs, identifiers with the most flagged events, delivery-failure spikes, and rate-limited and invalid-link events. Per-portal drill-downs show the same data scoped to one portal.
Admins, Super Admins, and people granted App admin for Portals. Settings can switch individual tabs (Catalog, Analytics, Audit Log, Security, Branding, Custom Domains) off for everyone.
No — strictly read-only by design. The Portals Agent assembles evidence; an admin makes the change — a portal is opened or closed on the Portals Catalog tab, its rate limits are set on the Identity & Recovery tab, and a token is revoked in the app that owns the portal.
Every portal takes its logo, colors and fonts from your workspace's Brand & Theme. Portals → Branding changes any of them for your public portals only, and Match workspace brand puts them back.
Let's Talk
Every team. Every employee. Every workflow. One AI platform — built for the frontline. Since 2008, trusted by 2 million+ users with an NPS of 78.
Why Choose Us?
- Frontline AI: Governed AI for every employee and workflow.
- Top Security: HITRUST, ISO & SOC 2 certified.
- Exceptional UX: Delightful on mobile and desktop.
- Proven Results: 98% customer retention rate.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
$42 per specialist a month · 10 minimum · 14 days free, $0 today. Or book a walkthrough first:
Prefer to explore first? Ask AI about Customer Portal Builder & Branded Partner Portals →