Sharing and installing workflows

The community gallery

Workflows published by other clinicians appear in a gallery you can browse. Each one shows its steps and sample output, so you can see what it produces before installing it rather than after.

Installing one

Installing gives you your own copy to run and edit. Your copy is independent from that moment: changes the author makes later do not reach it, and yours never reach theirs.

What happens to things you do not have

A workflow built in someone else's account refers to their Spaces, their reference documents and their templates. You do not have those.

Rhazes does not quietly drop them. The step stays, the reference is cleared, and the step is marked as needing your input, with the canvas showing how many steps need attention.

This is deliberate, and it is a clinical safety decision rather than a technical one. A retrieval step that silently lost its guideline would still run and still produce confident prose, only now with nothing behind it. A step that refuses to run until a human looks at it is the safer failure.

So an installed workflow is not ready to run until you have worked through what it flagged and pointed those steps at your own material. See Choosing what a workflow can draw on.

Publishing yours

When you publish, references to your Spaces and documents are stripped on the way out. They are your organisation's structure, they mean nothing in anybody else's account, and they should not travel with a shared workflow.

Before publishing, read it as a stranger would. Take out anything specific to you, and write a description that says plainly what it does and what it expects, because whoever installs it did not watch you build it.