---
title: HubSpot CMS-Hosted External Portal Architecture
description: See how WoodsPortal brings a customer-facing app, secure access and supported HubSpot records together, without building every screen from scratch.
---

[Skip to content](https://woodsportal.digitalwoods.io/en/resources/articles/hubspot-cms-hosted-portal-frontend#main-content)

[![WoodsPortal](https://woodsportal.digitalwoods.io/hs-fs/hubfs/woodsportal-2026/v3234/assets/woodsportal-logo.png?width=393&height=50&name=woodsportal-logo.png)](https://woodsportal.digitalwoods.io/)

[Product](https://woodsportal.digitalwoods.io/product) Use Cases

[Customer Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Vendor Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Dealer Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Membership Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal) 

[Pricing](https://staging.woodsportal.digitalwoods.io/pricing) Resources

[Browse all resources](https://woodsportal.digitalwoods.io/resources) [Documentation & help](https://woodsportal.digitalwoods.io/resources/docs) [Developer resources](https://developer.dev.woodsportal.com/) [Open-source frontend](https://github.com/Digital-Woods/WoodsPortal-Frontend) 

[Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo) 

Menu

[Product ↗](https://woodsportal.digitalwoods.io/product) Use Cases

[Customer Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Vendor Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Dealer Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Membership Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal) 

[Pricing ↗](https://staging.woodsportal.digitalwoods.io/pricing)

Resources

[Browse all resources↗](https://woodsportal.digitalwoods.io/resources) [Documentation & help↗](https://woodsportal.digitalwoods.io/resources/docs) [Developer resources↗](https://developer.dev.woodsportal.com/) [Open-source frontend↗](https://github.com/Digital-Woods/WoodsPortal-Frontend) [Get Started with WoodsPortal ↗](https://app.woodsportal.com/login/sso) [Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo)

[Resources](https://woodsportal.digitalwoods.io/resources)/Articles/How a HubSpot-Hosted Customer Portal Works

ARTICLE

# How a HubSpot-Hosted Customer Portal Works

See how WoodsPortal brings a customer-facing app, secure access and supported HubSpot records together, without building every screen from scratch.

**[WoodsPortal Editorial Team](https://woodsportal.digitalwoods.io/en/resources/author/woodsportal-editorial-team)**ArticleOctober 14, 2026

On this page

Imagine your customers need to check orders, support requests or project updates. The information already lives in HubSpot, but your customers need an easy way to use it. WoodsPortal provides the customer-facing experience, so your team can work with the records you already manage.

## Think of it as three connected parts

One portal, three jobs

Customer portal

What customers see and click

Secure connection

Checks identity and allowed information

HubSpot CRM

Where your team manages business records

A customer signs in, opens a request and sees the information their account is allowed to access. Their portal screens and the HubSpot records work together, while permission checks stay part of the setup.

## A familiar example

Maya works at Northstar Foods. She wants to see whether a cooling-unit service request has been resolved. Instead of emailing the service team, she opens the Northstar customer portal and selects her request.

From Maya's question to the right answer

Maya signs in

Northstar customer portal

Opens a request

Cooling unit stopped

Reads the update

Approved status and notes

The portal is the part Maya uses. HubSpot is where her service team manages the request. The connection brings the right information into the customer experience.

## What does 'hosted on HubSpot CMS' mean?

It means the customer-facing web application can be delivered through HubSpot's website system. WoodsPortal's frontend is built with modern web technology and runs as part of the configured HubSpot-hosted experience. This is different from using HubSpot's standard customer-support screens.

Hosting a web page and allowing customers to access CRM data are two separate jobs. A page on HubSpot does not automatically make every CRM record safe for external visitors. Your portal still needs an approved sign-in flow, permissions and a supported way to request the correct data.

## Do you need HubSpot Enterprise?

No—not simply to host the portal's frontend. WoodsPortal's nested object-relationship features use GraphQL, available with HubSpot Sales Hub Enterprise, Service Hub Enterprise, or Content Hub Professional or higher. Many other WoodsPortal use cases work through REST APIs on HubSpot plans including Free, depending on the configured features. CMS hosting rights and data/API access are separate.

HubSpot's own serverless functions are a separate Enterprise-level feature. WoodsPortal does not require those HubSpot serverless functions for its described implementation. Confirm the actual account entitlement and selected setup before deciding what can be used.

## What should you decide first?

A short setup checklist

1\. People

Who will sign in?

2\. Records

Which HubSpot items do they need?

3\. Permissions

What can each person see or change?

4\. Experience

Which pages and actions make their work easier?

Start with one real customer task. For example, 'Check my open service requests.' Choose the records, the approved fields, and the actions the customer should have. Test with two different customer accounts to check that one cannot open the other's information.

## When is this approach useful?

It suits businesses that want more than a basic ticket screen: projects and files together, partner requests, dealer information or customer-specific records. If you only need a simple customer ticket view, evaluate HubSpot's native support portal as well.

## Frequently asked questions

### Is WoodsPortal a replacement for HubSpot?

No. HubSpot remains the CRM where your team manages the supported records. WoodsPortal provides an external experience around that information.

### Does the customer need a paid HubSpot CRM seat?

External portal users are not automatically HubSpot CRM seats. Your HubSpot subscription and portal usage terms are separate.

### Does the portal have to use HubSpot CMS Enterprise?

No. The frontend itself does not automatically require CMS Enterprise. The chosen data integration, object types and HubSpot features determine which subscription is eligible.

### What is the difference between REST and GraphQL?

GraphQL powers WoodsPortal's nested object relationships and requires Sales Hub Enterprise, Service Hub Enterprise, or Content Hub Professional or higher. REST can support many other portal configurations on HubSpot Free and paid plans; the actual features depend on your setup.

### Can customers see every HubSpot record?

No. The experience must be configured to show only the records and actions each external user is permitted to access.

### Can the portal display files and related records?

Yes, in supported configurations. Nested related records use WoodsPortal's GraphQL implementation and an eligible HubSpot subscription. Simpler REST-based setups, including HubSpot Free, can support other views and actions according to their configuration.

### How should we start?

Pick one task, one customer group and a few example records. Test both the useful flow and access restrictions before expanding.

## Bring your HubSpot information to customers

See the WoodsPortal customer portal use case and the HubSpot CMS client-module guide to understand how the experience fits together.

[WoodsPortal customer portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) · [HubSpot CMS setup guide](https://woodsportal.digitalwoods.io/resources/docs/add-the-woodsportal-client-module-to-hubspot-cms)

KEEP EXPLORING

## Related resources

[Browse all resources ↗](https://woodsportal.digitalwoods.io/resources)

## On this page

[All resources ↗](https://woodsportal.digitalwoods.io/resources)

A connected experience

## Turn your HubSpot data into a customer workspace.

Explore how WoodsPortal presents connected records and relevant actions to external users.

[Explore the product ↗](https://woodsportal.digitalwoods.io/product)[Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo)

A CONVERSATION ABOUT YOUR PORTAL

## Book a meeting.

Choose a convenient time to discuss your HubSpot portal.

×

Prefer to open the booking calendar in a new tab? [Open meeting calendar ↗](https://digitalwoods.io/meetings/woodsportal/demo)

×

COMING SOON

## This resource is in preparation

We are preparing this resource for the WoodsPortal library. Explore other topics in the collection, or talk with our team about your portal plans.

Return to resources ↗

[![WoodsPortal](https://woodsportal.digitalwoods.io/hs-fs/hubfs/woodsportal-2026/v3234/assets/woodsportal-logo.png?width=393&height=50&name=woodsportal-logo.png)](https://woodsportal.digitalwoods.io/)

Your HubSpot. Their experience.A complete portal, ready to make your own.

[Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo)

## Product

[Overview](https://woodsportal.digitalwoods.io/product) [Pricing](https://staging.woodsportal.digitalwoods.io/pricing)

## Solutions

[Customer Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Dealer Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Vendor Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Member Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal)

## Resources

[Blog](https://woodsportal.digitalwoods.io/en/resources) [Knowledge Base](https://woodsportal.digitalwoods.io/resources/docs) [Developer Documentation](https://developer.dev.woodsportal.com/)

## Company

[DigitalWoods](https://digitalwoods.io) [Trust Center](https://trust.digitalwoods.io/) [HubSpot Marketplace](https://ecosystem.hubspot.com/marketplace/listing/woodsportal)

[Privacy policy](https://digitalwoods.io/privacy-policy)[Terms of service](https://digitalwoods.io/terms-of-service)[Frontend license](https://github.com/Digital-Woods/WoodsPortal-Frontend/blob/main/LICENSE.txt)

© 2026 DigitalWoods Technologies Inc.WoodsPortal is a DigitalWoods product.

Northstar, Horizon and Riverside scenarios and portraits are illustrative, not customer testimonials.

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "WoodsPortal Editorial Team",
    "url" : "https://woodsportal.digitalwoods.io/en/resources/author/woodsportal-editorial-team"
  },
  "dateModified" : "2026-10-16T10:36:39.291Z",
  "datePublished" : "2026-10-14T18:30:00.000Z",
  "headline" : "HubSpot CMS-Hosted External Portal Architecture",
  "mainEntityOfPage" : {
    "@id" : "https://woodsportal.digitalwoods.io/en/resources/articles/hubspot-cms-hosted-portal-frontend",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://woodsportal.digitalwoods.io/hubfs/digitalWoods%20logo.png"
    },
    "name" : "DigitalWoods Technologies Inc"
  }
}
```