How to Configure a Customer Support Portal in HubSpot
Set up a secure, logged-in portal where your customers can view, reply to, and manage their own support tickets — by connecting a domain, choosing who sees which tickets, and deciding how customers get access.
A customer portal (now set up as HubSpot's updated "support portal" experience) gives your customers a private, logged-in space to see and manage their own support tickets and reach your knowledge base. It's one of the higher-leverage things you can turn on in Service Hub: it brings transparency to the support relationship, reduces the steady stream of "what's the status?" emails, and makes your support operation feel organized and professional. The setup itself is short — the value comes from getting a few key decisions right. Here's how to configure it well.
What you need before you start
A customer portal requires a Service Hub Professional or Enterprise subscription, a domain connected to HubSpot to host the portal, and at least one live ticket pipeline — because the portal displays tickets, and only tickets. Conversations that aren't associated with a ticket won't appear. It's worth confirming all three before you begin, since a missing domain or an empty pipeline is the most common reason a portal setup stalls.
Decide who should see which tickets
This is the most important decision in the whole setup, because it controls what each customer can see when they log in. HubSpot gives you three visibility models: customers can see only the tickets they're personally associated with, all tickets from their company, or a hybrid where only selected contacts (those meeting criteria you define, such as a job title or a designated-contact property) can see company-wide tickets while everyone else sees only their own. Choose deliberately — this is what keeps one customer from seeing another customer's requests — and always test each rule with a real login before inviting anyone.
Choose how customers get access
You control who can get into the portal in one of two ways. With access group membership, you invite a curated list of contacts and HubSpot sends them a registration email — ideal when you have a defined set of customers. With self-registration, anyone can create their own login, which is enabled in your private content settings and suits a more open, low-friction portal. If you go the curated route, note that access-group limits are shared with your knowledge base, so it's worth planning them together.
Connect a domain and create the portal
In HubSpot, go to Service > Customer Portal and click Get Started. You'll name the portal (this becomes the browser-tab title your customers see), select the connected domain to host it on, and set the URL slug. Host the portal on your own connected domain rather than a default HubSpot system domain — a system domain won't send the membership emails that invite customers to register, which quietly breaks the invitation experience.
Set the support form and ticket routing
During setup you can add a basic support form so customers can open new requests directly from the portal (you'll set the button text and form title), or choose to skip the form if customers open tickets through other channels. You'll also select the inbox or Help Desk where tickets created through the portal are routed, so new requests land in the right place and get worked like any other ticket.
Customize the invitation and confirm member emails
Registration and invitation emails send to a contact's member email property, so confirm that property is populated for the people you're inviting — if it's blank, the invite won't reach them. Take a few minutes to customize the registration email so the invitation reads on-brand rather than like a generic system message; this is your customer's first impression of the portal, and it's worth getting right.
Review settings, hide internal details, and test
Before going live, review the portal's settings — how tickets appear, consent notices, and especially which ticket properties are visible. The portal surfaces ticket data, so make sure no internal-only properties (private notes, internal statuses, cost fields) are exposed to customers. If your account has Sensitive Data settings enabled, be aware that attachments sent through HubSpot can't be viewed outside HubSpot. Finally, log in as a test contact against each visibility rule to confirm every customer will see exactly what they should — and nothing more — before you send real invitations.
Pair it with your knowledge base
The portal is one half of a strong self-service experience; the knowledge base is the other. Customers typically reach the portal through the knowledge base, and the two share access groups, so setting them up together gives your customers a single, coherent place to find answers and track their requests. If your knowledge base isn't built yet, the portal still works on its own for tickets, and the knowledge base can be added separately.
If you want to learn more about how to configure a customer portal in HubSpot, contact The Gist.