Choosing what a workflow can draw on
Point a Rhazes workflow at your own guidelines, spaces and reference documents so its output follows local practice, not generic advice.
Updated
What the step sets
A Sources step decides what the workflow can draw on when it reasons: a Space and the reference documents in it, particular guidelines, or regional sources.
Why it matters more in a workflow than in a chat
In a chat you can see an answer drifting away from local practice and correct it. A scheduled workflow has nobody watching. Whatever it draws on is what goes into the output, unattended, every time it runs.
A review workflow pointed at your trust's protocol produces your review. The same workflow with no Sources step produces a generic one, and it will keep producing it.
Only what you can reach
Rhazes offers only sources you actually have access to. If a Space is not listed, either you are not a member of it or its documents are still processing and cannot be searched yet.
That restriction is also why a workflow shared by another clinician arrives with its source steps cleared and flagged for your attention. See Sharing and installing workflows.
Branching on what it found
A Sources step reports how many things it found, which you can branch on. That is how a workflow handles "we have a local protocol for this" differently from "we do not", rather than proceeding identically either way. See Branching on a condition.
Keep the scope tight
Point a step at the material that is actually relevant rather than at everything you have. A tightly scoped source produces a more specific answer, and retrieval across a very large space is slower.
See Spaces for setting up shared reference material.