Shared files are enough when
- Your team shares one stable file link and it rarely changes.
- You update press materials once a year or less.
- Different people can share their own copy without version drift becoming a problem.
Executive summary
Start here before deep docs
What it does, what it doesn't, and what to do next.
Use PressKit when your team is tired of tracking which press kit is current and who has the latest link.
- Each Company record gets one EPK profile with a stable public URL. Update the profile, the link stays current.
- Publishing is manual by default: the profile only goes public when you publish it. Auto-publish mode is available but irreversible once enabled.
- Quick Facts sidebar is off by default. Enable per portal in settings when ready.
- Images, documents, and video links are validated for format and size before publishing.
Best for
- Teams that update press materials per release cycle or campaign
- Operators managing EPKs for multiple HubSpot Company records
- Workflows where multiple people need current EPK access from one source
Not for
- One-time press kit creation with no ongoing update cycle
- EPKs for objects other than HubSpot Company records (v1 scope)
- Full media asset management or journalist outreach distribution
What changes
Your team runs this workflow every week. Here's what changes.
Before
Your team updates the press kit and sends a new link. The old link still circulates. Someone sends a journalist last quarter's version. No one is certain which file is current without asking.
After
One EPK profile lives on the HubSpot Company record. Update it there, and the public URL reflects it. No new link to send. No version to track down.
Free evaluation tier available. Install and validate one Company profile before broader rollout.
Install free in HubSpot → Read docs →Quick spec
What PressKit ships today
Concrete scope before deeper docs.
- EPK profiles: One EPK profile per HubSpot Company record.
- Required to publish (default mode): Artist Name and Description.
- Media inputs: image uploads, document uploads, HTTPS video links.
- Operator flow: Company record tab/sidebar → Prepare link → Open PressKit Editor.
- Quick Facts rail: off by default, toggleable per portal via epk.quickFactsEnabled.
- Public route: /epk/:portalId/:publicId.
Fit check
Google Drive / Dropbox vs PressKit
Use this before you install.
PressKit fits when
- Links go stale or the wrong version gets sent to press contacts.
- Multiple people need current EPK access from a single Company-scoped source.
- You need a consistent public URL that stays current as content changes.
Trust answers
Support hours: Monday-Friday, 9:00 AM to 5:00 PM America/Los_Angeles.
Response target: General support first response target: within 1 business day.
All scopes documented. Each HubSpot permission PressKit requests is listed with a reason before you install. Review scopes →
Visual proof
Real UI proof: editor and public route
Start with the shipped interface, then use the flow diagram for operator context.
/epk/:portalId/:publicId. Review Portal Settings for default vs auto-publish posture.Operator checks
- - Install: the published install link starts HubSpot authorization and returns to onboarding.
- - Settings: review Portal Settings, especially
epk.autoPublishByDefault(one-way). - - Public route contract:
/epk/:portalId/:publicId. - - Legacy route:
/epk/:publicIdis deprecated and returns404. - - Default mode publish gate: required
Artist NameandDescriptionmust be present before publish state changes. - - Visibility: default mode serves published records only; draft and missing records resolve as not found. Auto-publish changes the default—treat it as public-by-default visibility.
Walkthrough video coming soon. In the meantime, install the free tier and try it in your own portal. Install free →
Shipped behavior
Concrete behavior with explicit boundaries
Claims below reflect currently documented behavior.
Company card → PressKit Editor
Uses a HubSpot Company record card to prepare and open the dedicated PressKit Editor (Prepare PressKit Editor Link → Open PressKit Editor).
Portal settings (visibility + rendering)
Portal settings control visibility posture (including irreversible auto-publish), Quick Facts default-off behavior, public-page content defaults, hero behavior, video embed policy, and media limits. See Portal Settings.
Publish requirements
Default mode (auto-publish OFF): Artist Name and Description are required to publish. Auto-publish changes the visibility default (including empty profiles).
Media handling
Supports image uploads, document uploads, and HTTPS video links with media limits and MIME validation guardrails.
Public page contract
Public route contract is /epk/:portalId/:publicId. Default mode renders published records only; auto-publish mode makes pages accessible by default (including empty profiles).
Durable persistence
Profile source of truth is HubSpot Company properties. Uploaded images/documents are stored via the HubSpot Files API.
Operational safety controls
Includes production safety controls like readiness checks (/ready), portal-scoped API boundaries, write-rate throttling, and explicit 4xx/5xx error boundaries.
Metrics exposure
Emits route + EPK workflow metrics for internal operational dashboards and release checks.
Free tier available. Install and evaluate in your own HubSpot portal before committing to a paid plan. View pricing →
Operator flow
Roll out with fewer surprises
Use a narrow validation path before wider sharing.
Install + authorize
Install PressKit in HubSpot and complete OAuth authorization.
Choose your publish settings
Confirm default mode vs irreversible auto-publish in Portal Settings before wider access.
Open Company record and prepare editor
Open a HubSpot Company record and use the PressKit card to click Prepare PressKit Editor Link.
Open PressKit Editor and save
Click Open PressKit Editor, fill required fields (Artist Name, Description), add optional media (and Tribute to if used), then publish in default mode.
Stay current with docs
Use docs (including settings) to keep your configuration tied to documented behavior as the app updates.
Use cases
Workflow-shaped use cases
Examples reflect common press-kit publishing workflows in HubSpot.
Artist launch profile publishing
Default mode (auto-publish OFF): create a Company-linked EPK draft, run required-field/media checks, then publish to a stable external route.
Agency handoff without drift
Keep one canonical EPK profile on the Company record so internal and external teams edit the same source data.
Draft review before press outreach
Default mode (auto-publish OFF): hold the profile in draft while legal/comms review content, then publish only after approval with route verification.
Media pack refresh cycle
Update image/document assets and HTTPS video links in Company context with guardrails before each campaign wave.
Scope boundaries
Does | Does not
Each out-of-scope item includes why it is constrained and what to do instead.
Does
Manage one Company-based profile
One EPK profile per Company record keeps authoring and publish state deterministic.
Choose a public visibility posture
Default mode (auto-publish OFF): draft and missing records are not publicly accessible. Auto-publish mode (irreversible) makes public pages accessible by default, including empty profiles.
Use stable portal-scoped route
Public pages resolve at
/epk/:portalId/:publicId, with legacy route deprecation enforced.Enforce publish/media guardrails
Default-mode required fields plus media-limit/MIME checks keep public output predictable.
Share without accidental indexing
Public pages send
X-Robots-Tag: noindex, nofollowandCache-Control: no-store. PressKit is designed for sharing, not SEO.
Does not (and fallback path)
Per-company theming/layout customization
Why: v1 prioritizes stable baseline rendering. Fallback: keep brand variation in source media/content assets.
Password-protected public links
Why: public route contract is intentionally simple in v1. Fallback: distribute links through your own access-controlled channels.
Built-in analytics UI
Why: current scope centers on authoring/publishing reliability. Fallback: measure distribution outcomes in your existing analytics stack.
Act as your public marketing site
Why: PressKit pages are intentionally noindex/no-store. Fallback: use your website for SEO and use PressKit links for direct sharing.
Docs and trust
Decision-ready links
Everything needed to evaluate and operate PressKit.
FAQ
PressKit FAQ for HubSpot operators
Operational answers linked to scope and boundary docs.
Does PressKit support records beyond HubSpot Company objects?
No. PressKit is Company-record focused and manages one EPK profile per company. Multi-object or custom-object profiles are out of scope in v1. Review limitations.
Why are PressKit scopes required?
Scopes support install authorization, Company-record context, and required read/write operations for profile authoring and publish behavior. See Scopes and Permissions.
What is the uninstall or data deletion path?
Uninstall removes app access from HubSpot. If you have data deletion questions, contact support with your portal ID.
Need help evaluating? Ask a rollout question →