---
title: "The publishing workflow | Grafana Labs"
description: "Steps to follow to publish a plugin"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# The publishing workflow

Follow this order to submit your plugin:

1. Package the plugin, but don’t sign it yet.
2. Optionally, add a ready-to-run test setup for reviewers.
3. Run the plugin validator, a tool you run yourself to catch problems before you submit.
4. Submit the plugin:
   
   - In Grafana Cloud, go to **Org Settings** &gt; **My Plugins** and click **Submit New Plugin**.
   - You must have the Admin role in the organization.
   - The submission form asks for a public URL to your packaged plugin’s ZIP file, for example attached to a release in your Git repository, along with the file’s SHA1 hash and a URL to your plugin’s source code. Refer to [Publish or update a plugin](https://grafana.com/developers/plugin-tools/publish-a-plugin/publish-a-plugin) for all the fields in the form.
5. Wait for the review to finish.
6. Sign the plugin after it’s approved.

## Check these requirements before you submit

To be published in the Grafana plugin catalog, your plugin must meet certain criteria. For example, it has to use one of the accepted licenses: AGPL-3.0, Apache-2.0, BSD, GPL-3.0, LGPL-3.0, or MIT. Refer to the [Grafana plugins policy](https://grafana.com/legal/plugins/) for the full criteria.

Grafana Labs can also decline plugins that fork or duplicate an existing plugin, bundle several plugins into one, or only work in a specific environment.
