Skip to content

docs(studio-app): say brand kits are shared within the workspace only - #7570

Merged
ukimsanov merged 1 commit into
mainfrom
docs/brand-kits-sharing
Nov 11, 2026
Merged

ukimsanov merged 1 commit into
mainfrom
docs/brand-kits-sharing

Conversation

@ukimsanov

Copy link
Copy Markdown
Collaborator

What

Replaces the "Shared kits" section of the Studio app's brand kits page (docs/studio-app/brand-kits.mdx) with "Kits and your team":

  • Before: "Kits other people share with you appear under Shared with you. You can use them but not change them."
  • After: "Everyone in your workspace sees its kits under Yours and can use them in their projects. You can't share a kit outside your workspace from the Studio app, and kits made on app.heygen.com don't show up here."

The last sentence (only a workspace owner or admin can change the workspace's brand settings) is unchanged.

Why

The page implied you can share a brand kit with other people, but the Studio app has no way to do that, and kits made or shared on app.heygen.com don't appear in the app. Users asked how to share a kit and couldn't find it. This keeps the one true, useful fact (workspace members already see the workspace's kits) and says plainly that sharing outside the workspace isn't available, without promising it.

How

Text-only change to one section. No other page links to the old #shared-kits anchor.

Test plan

  • bun run lint passes
  • Page renders locally with mint dev (new heading and text present)
  • Checked the behaviour in the Studio app: a kit shared from app.heygen.com to a second account does not appear in that account's Studio app
  • Documentation updated

@mintlify

mintlify Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
hyperframes 🟢 Ready View Preview Nov 11, 2026, 9:07 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@heygengenesis heygengenesis Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked the new text against the Studio app (hyperframes-internal studio-app/src/brandKits) and the kit list it reads (EF cutroom/backends/brand_reads.py, GET /v1/brands). No blocker from me.

Accurate

  • Yours = owned, which is row.space_id == space_id. So every kit in the workspace shows there for every member, whoever made it.
  • The Studio app has no way to share a kit. The only share-related code is the read-only Shared with you section.
  • Kits made on app.heygen.com don't show. The list only takes kits that have a brand_profiles head row, and only Studio's create_kit writes one (_candidate_kits with_head). That matches your two-account test.

Optional (non-blocking)

  • The app still shows a Shared with you section (KitLibrary.tsx:133, and "Shared with you, view only" in the project picker). It lists HeyGen's preset kits and any Studio-made kit shared into the workspace through shared_resources. After this change the page never mentions that section, so a user who sees it gets no explanation. You could add a sentence such as: "Kits HeyGen provides appear under Shared with you. You can use them but not change them." Fine to leave it for a follow-up.

I'll approve once Rames has looked and found no blocker.

@ukimsanov

Copy link
Copy Markdown
Collaborator Author

Thanks. Leaving the optional sentence out on purpose: HeyGen's preset kits don't appear under Shared with you in the app either, so that sentence wouldn't be accurate. The section only fills in a case we're not documenting while sharing is low priority. It can get its own line if that changes.

@jrusso1020 jrusso1020 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed at 83e2e1aa3fe0b9155b69e30dfaca67258fe28850.

No blocker found. The revised section matches the current workspace-scoped kit list and its Yours grouping. Studio's kit actions do not offer external sharing; ordinary kits created on app.heygen.com lack the Studio profile required by this list. The page already states its sign-in and workspace-feature prerequisites, so it does not promise availability before those gates.

Read the full page and traced the list, grouping and available kit actions in the current Studio implementation. No references to the removed #shared-kits anchor were found in docs. No runtime tests or live account walk were run for this text-only change. The existing review's optional explanation of Shared with you can remain a follow-up.

Need: yes, remove misleading sharing guidance · Size: ok · Reuse: existing workspace visibility terminology · Simpler: direct wording · Structure: fine (checked adjacent page sections; no split)
Risk: low — documentation only.

Verdict: COMMENT — no blockers
Reasoning: The wording describes current workspace behavior without promising an external sharing feature.

— Rames

@heygengenesis heygengenesis Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving at 83e2e1aa: Rames found no blocker at this head, and my earlier check of the text against the Studio app and the GET /v1/brands list stands. The Shared with you sentence is still an optional follow-up.

@ukimsanov
ukimsanov enabled auto-merge November 11, 2026 21:03
@ukimsanov
ukimsanov added this pull request to the merge queue Nov 11, 2026
Merged via the queue into main with commit c218b37 Nov 11, 2026
62 checks passed
@ukimsanov
ukimsanov deleted the docs/brand-kits-sharing branch November 11, 2026 21:09
@terencecho terencecho mentioned this pull request Nov 11, 2026
3 of 4 tasks

This branch was successfully deployed

1 active deployment
staging - docs — 83e2e1aa Deployed Nov 11, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants