Skip to main content

PressKit Documentation

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

Applies to version/build: PressKit docs v1 baseline (released February 16, 2026; see changelog for updates)

Skip docs search

Search PressKit docs

Find setup, troubleshooting, limitations, scopes, changelog, and operational guides from this docs hub.

Showing 7 of 7 PressKit docs.

  • PressKit · Guide

    PressKit Documentation

    Operator docs for PressKit: setup, settings, limitations, scopes, troubleshooting, and changelog.

    /apps/presskit/docs

  • PressKit · Setup

    PressKit Setup

    Install PressKit, launch PressKit Editor from a Company record, validate settings/guardrails, and verify the public route.

    /apps/presskit/docs/setup

  • PressKit · Guide

    PressKit Portal Settings

    Portal-level PressKit settings that control publishing defaults, public page content, and media limits.

    /apps/presskit/docs/settings

  • PressKit · Limitations

    PressKit Known Limitations (v1)

    Intentional v1 boundaries for PressKit, why they exist, and what to do when you hit one.

    /apps/presskit/docs/limitations

  • PressKit · Troubleshooting

    PressKit Troubleshooting

    Common PressKit failure signals and operator triage steps before contacting support.

    /apps/presskit/docs/troubleshooting

  • PressKit · Scopes

    PressKit Scopes and Permissions

    Scope dependency summary for PressKit with least-privilege rationale.

    /apps/presskit/docs/scopes

  • PressKit · Changelog

    PressKit Changelog

    Release notes for the PressKit public docs surface on clevercat.app.

    /apps/presskit/docs/changelog

PressKit is a CleverCat operational utility for HubSpot: create and publish one Electronic Press Kit (EPK) page per HubSpot Company record.

This docs hub is written for operators. It describes what ships, what doesn’t, and how to validate behavior in a controlled rollout slice before you widen access.

Operator index

What it does (today)

  • Adds PressKit surfaces in HubSpot Company records (record tab and sidebar).
  • Opens the dedicated PressKit Editor to manage one Company profile (required: Artist Name, Description).
  • Stores draft / published state and provides a shareable public URL.
  • Default mode (auto-publish OFF): public route renders published records only; draft and missing records return not found.
  • Auto-publish mode (irreversible setting): public pages are accessible by default (including empty profiles); per-record publish toggling may be disabled.
  • Quick Facts rail is off by default and can be enabled per portal via epk.quickFactsEnabled.
  • Accepts images, documents, and HTTPS video links.
  • Enforces publish/media guardrails: required publish fields, HTTPS video URLs, media limits, and MIME checks.

Start small. Validate one portal and a handful of Company records before you roll it out broadly.

  1. Install and authorize PressKit in HubSpot.
  2. Pick 1–3 representative Company records for your validation slice.
  3. From a Company record, open the PressKit surface and launch PressKit Editor.
  4. Populate required fields (Artist Name, Description) and save.
  5. Decide your portal visibility posture: default mode vs irreversible auto-publish mode.
  6. Default mode: publish one profile and verify the public URL resolves at /epk/:portalId/:publicId.
  7. Review limitations and scopes before wider rollout.

Boundaries (read this before rollout)

PressKit does:

  • Manage one EPK profile per HubSpot Company record.
  • Keep public pages portal-scoped (/epk/:portalId/:publicId) with explicit publish semantics.

PressKit does not:

  • Support multiple public profiles per Company record.
  • Provide password-protected public links in this release.
  • Offer per-company theming/layout variants in this release.
  • Include a rich public engagement analytics UI in this release.
  • Treat the deprecated single-segment legacy EPK URL as retired (404).

Support intake checklist

When you contact support, include:

  • Portal ID
  • Company record URL
  • Whether epk.autoPublishByDefault is enabled
  • Public URL tested (if relevant)
  • Expected behavior vs actual behavior
  • Timestamp with timezone
  • Screenshots and any visible error text (including any requestId if shown)