Docs
Swagger

Dashboard

Components library

Assign store component licenses from your account library onto a website — one license per component type.

Assign from library — not a direct install
You don’t install a store package straight onto a website from a listing page as the primary admin flow. First obtain a license in your Store library, then open the website’s Components tab and + Assign license. Removing the component returns the license to your library.

Where in the app

Website sidebar → Components. You’ll see licenses currently assigned to this site, a link to your Store library, and (for admins) the assign dialog for available licenses.

End-to-end flow

  1. Get a license in the Store

    Browse store.macrocontent.dev. Claim or purchase a listing into your library (/me/library/).

  2. Open the website Components tab

    In the dashboard, select the target website → Components. Only owners and Admins can assign or remove licenses.

  3. Assign license

    Click + Assign license. The dialog lists licenses in your library that are not yet on this website. Assign one — the platform installs / activates the component for that site (technical install rows appear for debugging).

  4. Use on the live site

    With the SDK booted, store components load at runtime. Editors can place and configure them in the overlay. See Developers for custom components and store runtime notes.

Rules of thumb

  • One license per component type on a given website.
  • Unassign returns the license unit to your library so you can assign it to another site.
  • Technical installs (collapsible in the UI) show low-level install records — day-to-day you manage licenses, not raw installs.
  • Listings are either content (inherit your site styles) or styled (opinionated design). That choice is made by the publisher, not at assign time.

Do

  • Keep unused licenses in the Store library until a website needs them.
  • Assign only what editors will place — unused installs still count as site configuration.
  • Check Macro Score / listing details in the Store before buying.

Don’t

  • Don’t expect “install on website” without going through your library + Assign.
  • Don’t confuse dashboard Components with building custom components as a developer.
Automation with Management API

Tokens can use store component permissions (store.components:read / store.components:install, including the project_bootstrap preset in the catalog) under /management/store/*. Prefer the dashboard assign flow for humans; use the API for scripted site bootstrap. See Management API and Store API.

Publishers

Shipping a listing? Follow the Publishers handbook for bundles, Macro Score, and quality.

Store API

Public listings and authenticated library / install surfaces.

Developers — components

Build custom components and understand store runtime loading.