Every request in Run-Via belongs to exactly one workflow, and the workflow decides which department owns the request at any moment. The current owner is the only team whose inbox shows the request as actionable — everyone else sees it as read-only until it lands with them.

Routing is defined at the workflow level. A step can:

• Move forward to the next department in the sequence.
• Route to a specific department out of order, based on a field value on the

request (for example, high-dollar POs route to Finance before Legal).

• Split into parallel branches that must all resolve before the request advances.
• Return to a prior step if a reviewer sends it back for revision.

Configure routing from Admin → Workflows → [workflow] → Steps. Each step lets you set a default next step and optional conditional rules. Conditions compare a form field to a value; the first matching rule wins.

The system is authoritative about which workflow a request follows. A request stays attached to its workflow when you edit it, and routine route changes are applied as the request reaches later steps. There is one narrow live exception: changing an Approval team retargets pending inline approvals already waiting at that same step when the workflow is saved. Completed decisions and requests at other steps are unchanged. This prevents silent status shifts on in-flight work.