Skip to main content

PressKit Setup

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

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

This setup runbook is written for HubSpot operators. It assumes you want predictable rollout behavior, not surprises.

Start with a small validation slice (one portal, a few Company records), then widen access only after the boundaries match your workflow.

What you'll do in this guide

  • Install and authorize PressKit in one HubSpot portal.
  • Launch PressKit Editor from a Company record.
  • Validate required fields, media guardrails, and your portal publish posture.
  • Verify the portal-scoped public URL contract: /epk/:portalId/:publicId.

Quick links

Prerequisites

  • HubSpot permissions to install marketplace apps in the target portal.
  • At least one Company record to validate.
  • Browser access to https://epk.clevercat.app.

Recommended rollout slice (before you install)

  • Pick 1–3 Company records that represent “normal” data (not your messiest edge cases, and not your cleanest).
  • Decide your portal visibility posture:
    • Default mode (publish-gated)
    • Auto-publish mode (irreversible; always-on public visibility)
  • Decide what “published-ready” means for your team (at minimum: required fields + approved media).

1. Install and authorize

  1. Open Install app.
  2. Select the HubSpot account to connect.
  3. Review requested permissions and approve OAuth.
  4. Confirm you are redirected to the PressKit onboarding route on clevercat.app.

Expected result: installation completes and lands on the PressKit onboarding page.

2. Open PressKit from Company record context

  1. Open a HubSpot Company record.
  2. Open the PressKit surface in that record (record tab or record sidebar, depending on your layout).
  3. Confirm the card loads and shows editor + share actions.

Expected result: the card loads in Company record context.

3. Launch PressKit Editor

  1. Click Prepare PressKit Editor Link.
  2. When ready, click Open PressKit Editor.

Expected result: PressKit Editor opens in a new tab and loads the Company profile context.

4. Confirm portal settings posture (recommended)

Before you publish anything, review portal settings.

Key decision: whether your portal stays publish-gated (default) or enables irreversible auto-publish.

Expected result: operators understand whether public visibility is publish-gated (default mode) or always-on (auto-publish mode, irreversible).

5. Author required profile fields

  1. Enter Artist Name.
  2. Enter Description.
  3. (Optional) Enter Tribute to and/or other optional copy fields available in your editor UI.
  4. Save changes.

Expected result: required fields persist for this Company profile.

6. Add media

  1. Upload images.
  2. Upload documents.
  3. Add video links using https:// URLs only.
  4. Save changes.

Expected result: uploads respect media limits and MIME checks, and non-HTTPS video links are rejected.

7. Verify public visibility and route contract

Public route contract is /epk/:portalId/:publicId.

Default mode (auto-publish OFF)

  1. Switch the profile to published in PressKit Editor (publish requires Artist Name + Description).
  2. Return to the Company record PressKit card and use Copy PressKit URL or Open Public Page.
  3. Verify the public page resolves at /epk/:portalId/:publicId.

Expected result: published records are viewable publicly; draft and missing records return not found.

Auto-publish mode (irreversible portal setting)

  1. Treat the public page as accessible by default (including empty profiles).
  2. Return to the Company record PressKit card and use Copy PressKit URL or Open Public Page to get the portal-scoped URL.
  3. If publish/unpublish controls are disabled, that is expected in auto-publish mode.

Expected result: operators treat public visibility as always-on for that portal.

Boundaries (setup flow assumptions)

  • The public URL must be the portal-scoped format: /epk/:portalId/:publicId.
  • If epk.autoPublishByDefault is enabled, do not rely on draft privacy.
  • The deprecated single-segment route /epk/:publicId returns 404.
  • Password-protected public links are not available in this release.

Support intake checklist

When you contact support, include:

  • Portal ID
  • Company record URL
  • Whether the portal is default mode or auto-publish mode
  • Public URL tested (if applicable)
  • Steps you took (including which button you clicked)
  • Expected behavior vs actual behavior
  • Timestamp with timezone
  • Screenshots and any visible error text