# Release to the marketplace

> Release a version other people can install, and ask for the Verified badge.

Kind: guide · ~2 min · Verified v0.71.0 · Next: [Collect responses](https://pr-1635-stg.superartifacts.app/docs/collect-data.md)

![A template page with a pending review status and its Publishing panel.](https://pr-1635-stg.superartifacts.app/screenshots/docs/marketplace-review-light.a8c28c6d.webp)

*The Publishing panel: release, then ask for verification.*

You will have a released template people can find and install.

**Prepare a marketplace release**

```prompt
Help me release <template slug> to the Super Artifacts marketplace with super_release_template. Check my plan, the version, the sample and the private demo first. Tell me it goes live as Community at once, and what asking for verification would check. Ask for my consent before making the demo or personal sample data public.
```

## Before it is listed

Marketplace release needs a paid plan with template publishing enabled. `super_release_template` releases a recorded version, separately from saving a draft. Releases only move forward.

The release scans the template's runtime, sample and listing text for live secrets. A detected credential refuses the release. A public release is live at once, labelled **Community**: anyone can find and install it, and the label says nobody has checked it yet. Your account must be a week old, and the title, description, keywords, use cases, example prompts and your workspace name cannot say *official*, *verified* or *Super Artifacts* — the label is the only place a tier appears.

Every template carries one of three labels. **Official** is made by Super Artifacts. **Verified** means a moderator looked at that version and found it safe and as described. **Community** is everything else. Ask for verification from the template's page, or have your agent ask; the template stays live while a moderator looks. A later release that changes only prose or the sample keeps the badge; one that changes the runtime, the install prompt, its parts or what it collects is Community again until it is verified.

A public release with a private demo needs your explicit **demo consent**, which makes the demo public. Sample data containing personal details needs separate consent to be shown. Consent is a decision about the content you are exposing.

## The listing

![A public marketplace listing with the template preview and description.](https://pr-1635-stg.superartifacts.app/screenshots/docs/marketplace-listing-light.ed108273.webp)

*The listing shows the released version, not the newest draft.*

The listing carries its label, the preview, description, use cases and requirements. Ratings count from workspaces that built something with it. Reports flag problems for a moderator; enough of them from established accounts hide a Community template until a moderator decides. Workspaces that already installed it keep building and are told why.

## A bad revision

A rollback creates a new draft version carrying an earlier version's content. It does not erase history or move a release backwards. That new version still needs releasing. Restoring across a runtime change can be refused, because history holds file digests rather than old runtime bytes.

## Check it worked

The template's page shows its label. Once released publicly, its marketplace listing is visible straight away and **Install** uses the released version. A pending verification request shows on the page until a moderator decides.

Next: [Collect responses](https://pr-1635-stg.superartifacts.app/docs/collect-data.md).