One Home For Every Public Portal You Run
Portals is the umbrella that gives every public-facing portal in your business a single home. Each owning app keeps its own portal feature — Field Service's Customer Portal, Recruiting's Candidate Portal, Offboarding's Former Employee Portal, eSig's kiosk, Drive's public links. The cross-cutting concerns — catalog, identity & recovery, audit log, branding, custom domains, analytics — live here.
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, recovery method, and an "open preview" link. The umbrella reads from the owning app; it never overrides.
Configure Identity & Recovery Once
One home for OTP / magic-link recovery rate limits, identifier masking rules, and lockout thresholds — applied uniformly to every portal that opts in.
Search The Audit Log
Browse PortalRecoveryAudit 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, success rate, and conversion across every public portal in one dashboard. Per-portal drill-downs included.
Apply Branding And Custom Domains
Logo, colors, fonts, and custom CSS apply to every portal. Custom domain mappings let each portal live on its own subdomain.
Surface Security Signals
Anomaly detection on the recovery layer — failed delivery spikes, top offending IPs, identifier hash collisions. Signals route to the right owning app for remediation.
An Umbrella That Doesn't Take Over
Portals manages cross-cutting concerns without owning per-portal feature toggles. Catalog reads, never writes.
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 just catalogs it.
- Field Service Customer Portal — work-order status, technician ETAs, customer payments.
- Recruiting Candidate Portal — application status, interview scheduling, offer letters.
- Offboarding Former Employee Portal — final pay stubs, COBRA, tax docs.
- 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 PortalIdentityRecovery — a shared concern every portal opts into. Configure rate limits and masking once, applied everywhere.
- Default recovery method — magic link or OTP per portal that supports both.
- Rate-limit window + max — protect against enumeration and brute-force attacks.
- Identifier masking — emails and phone numbers are masked in audit and UI.
- 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 PortalRecoveryAudit — 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 packets — Portals Admin Agent assembles them 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.
See Field Service→ Recruiting Candidate Portal
Candidates check application status, accept interview slots, and sign offer letters. Recruiting owns the feature; Portals catalogs it.
See Recruiting→ Offboarding Former Employee Portal
Former employees access final pay stubs, COBRA forms, and tax documents on a dedicated subdomain.
See Offboarding→ AI Front Office Public Widget
The public booking widget on book.{slug}.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.
See E-Signature→ Drive Public Links
Anyone-with-link shares for files and folders. Drive owns the feature; Portals' audit log captures every recovery event.
See DrivePortals 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 PortalRecoveryAudit 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 max attempts: 5 per window per identifier (configurable); Default audit retention: 180 days (configurable).
See every portal at a glance
Open the Portals catalog to confirm which public surfaces are live in your business — Field Service Customer Portal, Candidate Portal, Former Employee Document Portal, AFO visitor surface, eSig kiosk, public Drive links, and so on. 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 PortalIdentityRecovery 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 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 LEVERAGE
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.
Audit log & retention
Every portal hit, recovery event, and token rotation lands in the same audit log Legal already uses for the rest of the platform.
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 — both audit-ready with FINRA-friendly retention.
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 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
Two paired Portals agents — daily-ops checks and audit-grade evidence assembly — read across every portal in the catalog, governed by the same permission model.
Pair Portals With Its Agents
Two paired agents — Portals Help (daily ops checks) and Portals Admin (audit-grade evidence assembly). Both are read-only by design; 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
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 catalog reads from the owning app; it never overrides.
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 via the PortalIdentityRecovery concern. When they do, recovery rate limits, masking rules, and audit retention are configured here, applied everywhere.
Yes. Portals supports per-portal custom domain mappings. The catalog shows the active domain for each portal, and admins manage mappings centrally.
Every recovery event — request, send, consume, fail, rate-limit, lockout — writes to PortalRecoveryAudit, 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, identifier-hash collisions, delivery-failure spikes, and lockout rates. Per-portal drill-downs show the same data scoped to one portal.
By default, admin and super_admin roles. The configuration_schema controls per-feature visibility (Catalog, Analytics, Audit Log, Branding, Identity & Recovery, Custom Domains) and which roles can see each one.
No — strictly read-only by design. Portals Admin Agent assembles evidence and recommends the owning app's admin UI for the actual fix. The umbrella never overrides the owning app's authority on its own portal.
Branding (logo, colors, fonts, custom CSS) is configurable at the Portals level and applied to every portal that opts in. Owning apps can override per-portal where the business requires it (a candidate-portal that needs to match a recruiting brand, for example).
Let's Talk
Since 2008, we've been building the workforce platform — earning the trust of 2 million+ users and an NPS of 78.
Why Choose Us?
- AI-Powered Platform: The most unified workforce experience on the planet.
- Top Security: HITRUST, ISO & SOC 2 certified.
- Exceptional UX: Delightful on mobile and desktop.
- Proven Results: 98% customer retention rate.
Trusted by Legendary Companies:
