Skip to main content

Templates and the Org Marketplace

A workflow template is a reusable recipe. You export a workflow as a template once; anyone in your organization can install it into their own project as many times as they want, with their own credentials.

Templates are the second mental model for sharing work. The first -- direct sharing -- is covered in Sharing a Workflow. The two are different in important ways, so we'll spell out the contrast as we go.

What a template captures​

When you export a workflow as a template, the platform ships the setup only by default -- the design of the work, not the content of any run:

  • The team and its agents (roles, perspectives, system prompts, their skills, and the team network)
  • The stages, in order, with their hooks and routing
  • Stage assignments (which agent does what at each stage)
  • Trigger definitions (schedules, webhooks)
  • Tool assignments -- where safe to transfer (e.g. references to Skills that exist platform-wide)

A template does not capture:

  • Your credentials (API keys, secrets)
  • Your project's documents
  • Run data -- the messages, document reads, and results from any run
  • Bindings to specific App installs

This makes a template safe to share by default: every export ships a sample run, but by default it's activity only -- the timeline of stages, agents, and tool activity, with all message and result content withheld. If you want to show people what the workflow produces, deliberately choose full content when you export -- only then do the run's messages travel with the template.

So a template is portable, but installing it requires the installer to bring their own credentials and pick which LLM configuration to use.

Exporting a workflow as a template​

Steps​

  1. Open your workflow.
  2. Click the menu in the page header and choose Export as Template.
  3. Give the template a name, description, and category. These show up in the marketplace UI when teammates browse for templates to install.
    • The description appears in full on the template card -- it's no longer truncated -- so keep it to a sentence or two. The field is capped at around 240 characters.
    • You don't pick a difficulty: it's set automatically from the workflow's complexity, so you never have to choose it.
  4. Optional: add an About this template note. This is a free-form Markdown field for origin, credits, or any context that helps people browsing the library -- where the idea came from, who built it, links to background. It's separate from the description, and unlike the description it is not carried onto a workflow when someone installs the template; it stays with the template in the library only.
  5. Choose what the sample run shows: Activity only (default -- the timeline with all content hidden) or Full content (the run's messages and results become visible to everyone who can see the template -- only for runs holding no private data).
  6. Click Export. The template is created in your organization's marketplace.

# TODO screenshot: Export as Template modal with name, description, category fields

Your original workflow is unchanged. The template is an independent copy of the recipe.

Installing a template​

Steps​

  1. Open the Templates page in the sidebar.
  2. The page has two tabs: Platform (templates shipped by ORQO) and Organization (templates exported by people in your org).
  3. Click a template card to preview it. The preview shows the Workflow network (its stages and routing) and the Team -- the agents, each agent's LLM, and their skills -- plus any feature tags. The sample run's timeline appears under Messages; its actual content is visible only when the author exported with full content.
  4. Click Install.
  5. Pick the target project (where the new workflow will live) and the LLM configuration (which models to use, on which credentials).
  6. Click Install to confirm.

# TODO screenshot: Template detail page with the Install button and project/LLM config selectors

A fresh workflow appears in your project, owned by you. From now on it's your workflow -- you can edit it, share it, run it, export it again, all independent from the original.

Templates vs. direct sharing -- the mental model​

This is the comparison most teams need to internalize:

Direct share (Runner / Inspector)Template
Number of copiesOne -- everyone runs the same workflowMany -- each installer has their own copy
Runs as whose credentials?The creator'sThe installer's
Recipient can edit?No (creator-only)Yes -- it's their workflow now
Recipient can re-share / re-export?Only the creator canYes -- they own their copy
Best for"Press this button for me""Here's a recipe everyone should adapt"

Direct share = delegation. "Run my workflow, on my credentials."
Template = recipe. "Here's how to do it; build your own."

If you find yourself wanting to share a workflow with five people and they each have different credentials anyway, you want a template. If you want everyone to converge on the exact same execution path with the exact same credentials, you want a direct share.

What about credentials?​

When you install a template, none of the original creator's credentials come with it. That's a deliberate safety property: secrets never cross between members.

After install, you may see warnings like:

"This workflow uses a credential 'STRIPE_API_KEY' that doesn't exist in your account. Add it under Settings → Credentials before running."

This is normal. The template references a credential by name; you supply the actual value. Add the missing credential (or rebind the workflow's stages to a credential you already have), then run.

Editing and deleting templates​

Only the creator of a template can edit or delete it -- with one exception: an admin of the organization can also edit or delete org templates, since they own infrastructure.

Editing an existing template doesn't retroactively change the workflows that were installed from it. Each installed workflow is independent from the moment of install.

Platform vs. org templates​

The Workflow Library has two tabs:

  • Platform -- production templates shipped by ORQO and visible to every organization. You can install them but not edit them. (ORQO's learning demos live on their own page, Learn ORQO -- see the templates reference.)
  • My Org -- templates exported by members of your org. Visible only to your org.

Publishing a template platform-wide (visible to every organization) is reserved for the ORQO team -- it's the same Export action, with a "Publish platform-wide" option that only ORQO admins see. Your own exports always stay within your organization.

Learn more​