Skip to main content

How to manage press kits in HubSpot | PressKit

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

This guide reflects current shipped behavior.

HubSpot stores your company data well. Press kit management — keeping that data published, current, and accessible to media — is a separate workflow that HubSpot doesn’t handle natively.

PressKit is a CleverCat operational utility for HubSpot: one EPK profile per Company record, published on purpose, with a public URL that doesn’t change.

Fast answer

Native HubSpot baseline (manual)

  • Store press materials (bio, images, media links) in HubSpot Company property fields or notes.
  • Export or copy content manually into a page builder, PDF, or email when media requests come in.
  • Maintain separate public press page outside HubSpot, keeping it manually in sync with CRM data.

When native is enough

Manual press kit handling works when media requests are infrequent, content changes rarely, and one person manages all press material distribution.

Where native breaks

  • Content drifts between CRM and published materials: the PDF goes out, the Company record gets updated, the PDF doesn’t.
  • No shared public URL means every media request triggers an email chain for the latest version.
  • Multiple people managing press materials create version conflicts.
  • Draft-vs-published state requires manual discipline — there’s nothing enforcing it.

Operational utility path

Use PressKit when press materials change with release cycles or campaigns, multiple people need access without email chains, and you need a consistent public URL per Company that stays current.

Why this is harder than it sounds

  • Press kit content lives at the intersection of CRM data and public publishing — two different operational surfaces that rarely stay in sync manually.
  • Media outlets and journalists need a URL they can bookmark, not a PDF attachment that’s outdated by next quarter.
  • Team handoffs during campaigns create version conflicts: one person publishes an update, another resends the old PDF.
  • Required-field gaps — missing bio, missing key image — create publish-readiness gaps that go undetected until a media request arrives.

What you’ll get (PressKit)

  • One EPK profile per HubSpot Company record: Company-context workflow opens the PressKit Editor.
  • Default mode (auto-publish OFF): requires Artist Name and Description before publish, preventing empty page publication.
  • Supported media: image uploads, document uploads, and HTTPS video links.
  • Public route contract: /epk/:portalId/:publicId — a consistent URL per Company that stays current across content updates.
  • Draft/publish controls: explicit state management keeps unpublished content private.
  • Portal Settings: auto-publish-by-default mode available (irreversible) for teams that need public-by-default posture.

Prerequisites

  • PressKit installed in your HubSpot portal.
  • A test Company record for first-run validation.
  • Decision on visibility posture: default mode (draft-first) vs auto-publish-by-default.
  • Agreement on required fields before publish in your portal context.

Boundaries and limitations

Does

  • Keep press kit authoring and public publishing in one HubSpot-centered workflow.
  • Provide a consistent public URL per Company that stays current.
  • Enforce required-field publish gates in default mode.

Does not

  • Provide password-protected public links.
  • Support EPK profiles for objects other than HubSpot Companies.
  • Replace full media asset management systems.
  • Provide press release distribution or journalist outreach tools.

Validation slice checklist (before rollout)

  • Pick one test Company record and create a draft profile with minimal required fields.
  • Confirm the public URL is not accessible while in draft (default mode).
  • Publish and verify the /epk/:portalId/:publicId URL renders correctly.
  • Upload one image and one document; add an HTTPS video link; confirm all render on the public page.
  • Edit the Company profile and confirm the public page updates without changing the URL.
  • Review Portal Settings before enabling auto-publish-by-default (it’s irreversible).

Support-intake checklist

When contacting CleverCat support, include:

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

Fallback: use Known limitations and Support with portal context.

Next steps

FAQ

Is there one press kit per Company record, or can a Company have multiple?

One EPK profile per HubSpot Company record. This keeps the public URL consistent and the content relationship clear.

What happens to the public URL when I update the press kit content?

The URL stays the same. Content updates are reflected on the same /epk/:portalId/:publicId route without a URL change.

What fields are required before I can publish?

In default mode (auto-publish OFF), Artist Name and Description are required before publishing.

Can I give media a URL they can always share?

Yes. The public route contract means the URL you share with media stays current across all future content updates.

Is the press kit visible to the public while it’s in draft?

No, in default mode. Unpublished or draft profiles are not publicly accessible. Auto-publish mode changes this posture — review Portal Settings before enabling it.

HubSpot does a lot. Why add PressKit?

HubSpot does a lot. For everything else — Company-based press kit publishing with draft controls and a permanent public URL — there’s CleverCat.