# Publish a plugin: review, versions and suspension

Source: https://frosvo.com/docs/publish-a-plugin
Updated: 2026-11-12

How a plugin you build goes from draft to the marketplace, what is locked once it is submitted or published, what a new version needs, and what happens when Frosvo suspends a plugin.

A plugin runs on your servers; Frosvo calls it and it may call back with an API key. Because customers trust what was reviewed, the reviewed parts are fixed. This page is for developers who build plugins and publish them for other Frosvo workspaces.

## Before you start

- You need to be an owner of a workspace. Open the **Plugins** screen and the **Build your own** tab.
- A public plugin needs a privacy policy address and a support email.
- Drafts are private to your workspace. You can install your own draft to try it.

## How does a plugin get published?

1. Choose **Build your own**, then add a plugin: name, description, category and at least one address Frosvo should call (events, panel, actions or a page in a frame).
2. Choose the API scopes and events it needs. Ask only for what it uses.
3. Add the privacy policy and support email, and choose **Submit for review**.
4. A Frosvo reviewer approves it or rejects it with a note you can read. After a rejection you can edit and submit again.
5. Once approved it appears in the marketplace for every workspace.

## What is fixed, and when?

The reviewed parts are the **events address, panel address, actions address, frame address, API scopes, events and the settings form** your customers fill in. They are fixed:

- **While the plugin is in review.** The reviewer must approve what you submitted. If something changes between submitting and approving, the approval is refused and the plugin has to be rejected and submitted again.
- **Once it is published.** Customers agreed to that version.

The listing text (name, tagline, description, links, icon and colour) can still be improved at any time.

## How do I release a new version?

Once a plugin is published, open it under **Plugins → Build your own** and choose **Versions & sandbox**. Under **Release a new version**, enter the version number (three numbers, like 1.2.0, higher than every earlier one), say what changed (installers read this), and change any addresses, scopes, events or settings fields the new version needs.

- **Nothing reviewed changed:** the version goes out straight away and installs move to it.
- **An address, scope, event or settings form changed:** the version is **submitted for review**. One version can wait for review at a time. The version already on your customers' workspaces keeps running until the reviewer approves.
- **After approval, installers may need to accept.** If the new version asks for more access, more events, or sends data to a different host, each installed workspace is **paused** until its owner chooses **Accept update**. Nothing is sent to the new address before then. Versions that only reduce what the plugin can see or send, or keep it on the same host, apply to everyone automatically.

Every version stays in **Version history** with its changelog and review result. Installers see the version they are on, and a notice when an update is waiting.

### Try it first: the webhook sandbox

In **Versions & sandbox** you can send a signed sample event to your events address and see what your server answers. Sample events are clearly fake (they carry `sandbox: true` and example data) and nothing real is sent. Use it to check your signature verification before you release.

### Paid plugins and licence keys

You can show a price and a purchase link on your listing and tick **Require a licence key on install**. Frosvo does not take payment: customers buy from you, then paste the licence key you gave them when they install. The key is sent to you in the signed `plugin.installed` event. If you decide a key is not valid, call Frosvo's signed licence callback and that install is paused until you confirm it is valid again and its owner switches it back on.

## What happens if a plugin is suspended?

Frosvo can suspend a plugin that misbehaves. Right away:

- its panels and buttons disappear from every workspace;
- it stops receiving events;
- the API key given to each install is revoked, so it cannot read or write any more.

You see the reason as the review note. When a plugin is reinstated, its panels, events and API keys work again. If the problem was a leaked secret, rotate it first in the plugin's settings.

## Common problems

- **"The addresses, scopes, events and settings form of a published plugin can't change in place. Release a new version instead."** Edit it through **Release a new version** (under **Versions & sandbox**) instead of the plugin form.
- **"This plugin is being reviewed, so its addresses … can't change."** Wait for the decision, then edit.
- **"It was changed after it was submitted."** The reviewer sees this when the plugin's addresses or scopes changed during review. Resubmit after the rejection.
- **Customers say the plugin stopped working.** Check the review note for a suspension. If the plugin is fine, ask customers to check the plugin is switched on in their workspace.

## Related

See [plugins](/docs/plugins), the [developer hub](/docs/developers), [platform plugins](/docs/platform-plugins), and [security](/docs/security).

## Common questions

### Why can't I change my plugin's addresses after publishing?

Customers installed the version that was reviewed. If its addresses, scopes, events or settings form could change silently, an approved plugin could become something nobody approved. Release the change as a new version instead: it is reviewed, and installers accept it if it asks for more access.

### What can I still change after it is published?

Its name, tagline, description, links, icon and colour. Anything that changes what Frosvo calls or what the plugin may reach is locked.

### What happens to customers when a plugin is suspended?

Its panels and actions stop at once, it stops receiving events, and the API key it was given stops working. If Frosvo reinstates it, all of that comes back.
