Skip to main content

How to publish an EPK from HubSpot | PressKit

Last updated: March 22, 2026 (America/Los_Angeles)

This guide reflects current shipped behavior.

HubSpot is good at storing Company data. Publishing a public page from that data is a separate operational workflow. This page covers the manual baseline, then the PressKit path: explicit draft/publish control with one public route contract.

PressKit is a CleverCat operational utility for HubSpot: one EPK profile per Company record, published on purpose.

Fast answer

Native HubSpot baseline (manual)

  • Store company profile fields manually on HubSpot Company records.
  • Build/publish public press pages or company pages outside a dedicated EPK publish flow.
  • Manually keep CRM content and public page content aligned.

When native is enough

Native/manual handling is enough when publish volume is low and content sync risk is minimal.

Where native breaks

  • Draft-to-publish governance is easy to drift.
  • Public page consistency can diverge from CRM source data.
  • Media and publish checks require repeated manual coordination.
  • Route consistency and publish-state control are difficult without a single contract.

Operational utility path

Use PressKit when you want one EPK profile per HubSpot Company record with explicit draft/publish controls and portal-scoped routing.

Why this is harder than it sounds

  • Company profile data and public publishing are different operational surfaces.
  • Required-field gaps can block reliable publish readiness.
  • Manual handoffs increase content drift across teams.
  • CRM editing and public publishing are different operational workflows.

What you’ll get (PressKit)

Teams move from a manual “copy CRM data into a page builder” process to one operational flow:

  • One EPK page per HubSpot Company record.
  • Company-context workflow to open the PressKit Editor.
  • Default mode (auto-publish OFF): publishing requires Artist Name and Description.
  • Supported media: images, documents, and HTTPS video links.
  • Public route contract: /epk/:portalId/:publicId (the deprecated single-segment legacy URL is not current).
  • Portal setting auto-publish-by-default (irreversible) changes public access posture; review Portal Settings.

Prerequisites

  • PressKit installed in your HubSpot portal.
  • A test Company record for first-run validation.
  • Agreement on your portal’s visibility posture (default mode vs auto-publish-by-default).

Boundaries and limitations

Does

  • Keep authoring and publish controls explicit (draft vs published).
  • Use the portal-scoped public route contract.
  • Encourage test-slice validation before broad rollout.

Does not

  • Expand to multi-object profile management in current release.
  • Provide password-protected public links.
  • Treat the deprecated one-segment legacy EPK URL as current.
  • Replace rollout validation before broader use.

Validation slice checklist (before rollout)

  • Pick one test Company and create a draft profile with minimal fields.
  • Confirm the public URL is not accessible while in draft (default mode).
  • Publish; confirm /epk/:portalId/:publicId renders and the share URL matches.
  • Upload one image and one document; add one HTTPS video link; confirm render.
  • Edit the Company profile and confirm the public page stays stable.
  • Review portal settings before enabling auto-publish-by-default anywhere (it’s irreversible).

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID + Company ID/URL.
  • Profile status (draft/published) and publicId/share URL.
  • Steps to reproduce + screenshots of Editor and public page.
  • Media details (file type, size) or video URL used.
  • Any error message/request ID shown.

Fallback: use Known limitations and Support with portal context.

Next steps

FAQ

Is PressKit one profile per Company record?

Yes. One EPK profile is managed per HubSpot Company record.

Which fields are required before publish?

Default mode (auto-publish OFF) requires Artist Name and Description before publish.

What media types are supported?

Image uploads, document uploads, and HTTPS video links.

What is the public route contract?

Published records render on /epk/:portalId/:publicId.

Are unpublished records public?

Default mode (auto-publish OFF): no — unpublished or missing records are not publicly accessible. Auto-publish mode can make public pages accessible by default (including empty profiles); review Portal Settings.

Is the deprecated single-segment EPK URL still current?

No. The portal-scoped route is the current contract; the deprecated single-segment URL is not.

Can I publish directly from HubSpot Company context?

Yes. PressKit is Company-record-centered for EPK authoring and publish flow.

Where should procurement/security reviewers start?

Use docs, scopes, limitations, and trust pages before broader rollout.