Sharing a template

When a template works well enough that someone else could use it, you can share it to the library. This walks through what happens.

Before you start

You have to be an owner of the workspace the template lives in. Editors can build and run templates; publishing one outside the workspace is an owner's decision.

It is worth doing two things first, because both are much easier to fix before review than after:

• Run it once from scratch. A template that only works because of something left over in your workspace will not work for anyone else.
• Check the inputs. File inputs travel as names. If yours points at interview-final-v3.mp4, everyone who installs it starts with a step pointing at a file they do not have. A folder name such as broll is kinder.

Sharing it

From the template editor, open the editor's menu, choose Settings, then Share to library under Actions. The dialog collects a name, a description, tags and an icon, and shows you three things worth reading before you send it.

The exact YAML that will be published. This is what reviewers and installers see. If there is anything in a prompt you would rather not publish, this is where you notice.

What installers will need. Any service keys the template requires, listed by name. Keys are never carried across: this is telling installers what they will have to supply.

Anything the check found. Some findings stop the submission: it does not parse, the steps do not fit together, or something looks like an API key pasted into a setting. Others are warnings you can send anyway: an absolute path from your own machine, a link or an email address in a prompt, an unusually long piece of text.

You also confirm you have the right to share it, and agree to the community contribution terms. That is what gives us the right to host it and other people the right to use it.

What happens next

Your submission goes into a review queue. Someone reads it: not just the automatic checks but the prompts, the description, and what the template actually does compared with what it says it does.

You can watch its status under My submissions. It ends up in one of three places:

• Published. It is in the gallery. Your name appears on it, unless you chose to publish anonymously.
• Rejected, with a reason. Fix what the reason says and send it again; resubmitting puts it back in the queue with a clean slate.
• Still waiting. Review is a person, so it takes as long as it takes.

Afterwards

You keep ownership. Sharing grants us the right to host and distribute it, and other users the right to use and adapt it, including in paid work. It does not transfer anything.

You can withdraw it at any time. It disappears from the gallery. Copies people already installed keep working, which is the trade that makes the whole thing usable: an installer's video cannot break because someone else changed their mind.

Later edits do not follow it. What you submitted is a snapshot. Editing your workspace template afterwards changes nothing in the library, and if you want to publish the improvements, share it again.

Sharing a block instead

If what you built is a reusable piece rather than a whole pipeline, share it as a block. See Authoring a block.