Skip to main content

Sharing a Workflow

Workflow sharing has a knob that project and trigger sharing don't: the view mode. It controls whether your teammate opens the full builder or just a Run button.

Two view modes​

ModeWhat the recipient sees
Inspector (default)The full workflow builder. Every stage, every agent, every prompt. Read-only, but they can study how it works.
RunnerA streamlined card with the workflow's name, description, and a big Run button. Run history is shown as a compact list with chip badges; details open in a modal. No anatomy.

Both modes let the recipient run the workflow. The difference is whether they can see how the sausage is made.

# TODO screenshot: side-by-side comparison of Inspector view (Visual Builder canvas) and Runner card (hero + Run button + recent runs list)

When to use Inspector​

Pick Inspector when the recipient is technical and either:

  • Helping you build, debug, or extend the workflow
  • A senior reviewer who wants to understand exactly what's happening
  • Going to copy the workflow as a starting point for their own (in which case, also consider exporting it as a template)

Inspector preserves the full mental context of the workflow. Nothing is hidden.

When to use Runner​

Pick Runner when the recipient is non-technical and just needs the result. Classic cases:

  • A non-technical colleague who needs to push the button to generate a weekly report
  • A client or stakeholder who should be able to run a workflow on demand without seeing prompts
  • Anyone who would be intimidated or confused by the builder canvas

Runner is the "lend a workflow to someone who just needs to push the button" mode. It's the differentiator that makes ORQO usable by people who are not LLM engineers.

Sharing in Runner mode​

Steps​

  1. Open your workflow.
  2. Click Share in the page header. The Share drawer opens.
  3. Find the teammate in the list (or type their email/name).
  4. In the Mode dropdown next to their name, choose Runner.
  5. Click Share.

# TODO screenshot: Workflow Share drawer with the Mode dropdown expanded showing "Inspector" and "Runner"

The teammate immediately sees the workflow in their sidebar. When they click it, they land on the Runner card -- not the builder.

What the Runner sees​

The Runner view has two zones:

  • Hero card (left) -- The workflow's name, description, and a single Run button. If the workflow requires input, a hint appears: "You'll be asked for input on the next page."
  • Recent runs (right) -- A compact list showing who ran the workflow, when, and the status. Clicking a run opens a simplified detail view with chips and modals -- never the full builder canvas.

This is by design. A non-technical user should never need to think about stages, agents, prompts, or routing.

Credentials in shared workflows​

When you share a workflow, you're sharing execution authority over your workflow -- but not your credentials directly.

Concretely:

  • The workflow runs with the credentials you bound at design time as its creator.
  • The recipient running the workflow uses those same credentials -- they never see the API keys, just the result.
  • If you revoke the share, the recipient loses access immediately. No lingering token authority.

This is what we call credential delegation: you're lending the workflow's execution context, not the secrets behind it.

Changing or revoking access​

Open the Share drawer again to:

  • Change view mode -- flip a teammate from Runner to Inspector or vice versa
  • Unshare -- click the X next to their name; access ends immediately

When to share vs. when to export as a template​

Sharing and exporting solve different problems:

  • Share when you want a teammate to run your workflow on your credentials. There's exactly one copy.
  • Export as template when you want teammates to install their own copy into their own project, running on their own credentials. There are many copies.

For a deeper comparison, see Templates and the Org Marketplace.

Learn more​