# Release to the marketplace

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

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

## Goal

Release a recorded template version for other people to install.

## What you'll have

A public or unlisted release, separate from your latest draft.

## Needs

An eligible paid plan, a recorded template version and permission to release it. Public publishing requires an account at least seven days old. Check the sample and demo for content you would expose.

## Prompt

**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.
```

## Steps

### Before it is listed

1. Review the runtime, sample, guidance and listing. Release scans for live credentials and refuses detected secrets. Public listing text and the publisher name cannot claim reserved tier wording such as “Official”, “Verified” or “Super Artifacts”.
2. Release with `super_release_template` or the template's publishing controls. Public releases are discoverable immediately; unlisted releases install by slug without appearing in the marketplace. Releases move forward only.
3. Give explicit demo consent before exposing a private demo, and separate consent for personal sample data.
4. Request verification if wanted. **Official** identifies platform-made templates. **Verified** means a moderator checked that version for safety and accuracy. Other releases are **Community** while review is pending.

### The listing

The listing describes the released version, with preview, use cases and requirements. Ratings count from workspaces that built with it. Reports can hide a Community listing while moderation decides; existing installs remain usable.

A Verified badge survives sample or descriptive changes, but runtime, install-prompt, parts or data changes require another verification.

### A bad revision

Rollback creates another draft from recorded content; it neither erases history nor moves a release backwards. Runtime or data-model differences can prevent rollback. Review the refusal and save a new revision instead.

## Check it worked

The template shows the released version and tier. A public listing is discoverable, and a new installation resolves the release.

## If not

Read the release refusal. Public releases allow 10 per day, three per template per hour and 20 public templates. Fix credentials or reserved wording rather than bypassing the checks.

## Variations

A Team or Business workspace shelf shares privately with that workspace instead of the marketplace.

## Next

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