HubSpot Memberships Portal: Syncing File Access Across Custom Objects, Companies, and Contacts

A travel consortium asked us to recreate its member portal on HubSpot Memberships. Every member logs in to the same place, but what they find there depends on the licenses their company holds.

That single detail set the shape of the project. About five months went into getting the data part right, then building and testing the infrastructure on top of it. The portal has since soft-launched to a select group of members, with a wider rollout planned for the coming weeks.

Access That Belongs to the Company

In this portal, access isn’t a tier a person picks up at sign-up. It comes from licenses, and a license belongs to a company. Each one opens a defined set of files, and a company can hold more than one.

Employees inherit whatever their company holds. The CRM therefore has to carry the same answer in three places: on the license, on the company, and on every contact who works there. If those fall out of step, a member sees the wrong files.

One Source of Truth: The License Object

The design rests on a single decision. A custom object represents the license, and it’s the source of truth. Each record gives a company, and through the company its employees, access to certain files. Every other record takes its answer from there.

Taking an answer from there is the hard part, because a company can be associated with several license records at once. The access information sits across separate custom objects, and the company has to reflect all of them.

Passing Access Down to Companies and Contacts

We built a workflow that pulls the access information from each of those custom objects and passes it to the associated company. From the company, the same access syncs to the associated contacts. Every contact ends up with a synced property that reflects what their company’s licenses allow.

A person’s contact record now carries the answer. The files they can open follow from that one property.

Putting the Files Behind the Property

The files came last. We built a HubDB table listing everything available in the portal, and each member sees only the files their synced property gives them access to. A Senior Designer set up the membership pages and the HubDB table, working with our Data Architect. The build used Content Hub and Sales Hub and didn’t involve any third-party integrations.

Where It Stands Now

For members, the result is a new portal with a clean experience. The first rollout is a soft launch to a select group, and the client plans to expand it in the coming weeks. It’s early for adoption numbers, so we aren’t citing any.

The change is already visible on the client’s side. The files and how they were organized used to live in spreadsheets. They now live in HubSpot, in a HubDB table that’s easier to manage.

Planning a Portal With Similar Access Rules?

This build centered on access that depends on company-level licenses, not a single member tier. If you’re planning a HubSpot portal with rules like these, talk through your access model with our team.