As a workflow author, you may want to develop and edit the workflow until you are happy with how it works. But we also understand the importance of version control, particularly when workflows are shared within an organization. In this article, we describe the various states that a workflow can be in, and how we set you up for version control.

When a workflow has just been created, it is in a draft state. Draft workflows will show the word "DRAFT" at the top-right of the workflow card. They will also show a hard hat icon to the left of the workflow name, indicating that this workflow is still under construction!

Draft workflows can be run any number of times on the same sample. You can continue to edit the workflow script as often as needed. For the purposes of version controlling, you will want to publish your workflow so as not to accidentally change it. Draft workflows, including their output files and details on the job run, are only visible to the author. They cannot be seen by other members of your organization.

Once you publish a workflow, the icon to the left of the name no longer wears a hard hat! The workflow will no longer say "DRAFT" at the top-right, but will instead indicate if the workflow is a "NEXTFLOW" or "SCRIPT" type of workflow.

Published workflows with a particular set of arguments can only be run once on any given sample. You can run a published workflow with different argument values on the same sample.

If you click to edit a published workflow, you may edit the name and description only. The script, versions or repositories cannot be edited.

If you are part of an organization, you will also have the opportunity to select if this workflow should be run automatically for all new samples uploaded to your account and the accounts of any other users within your organization!

If you are part of an organization on One Codex, any workflows that you publish, or any workflows published by other workflow authors of your organization, become available to all organization members. Workflows created by other members within your organization will be distinguished with an organization symbol to the left of the workflow's name (see example below).

Other organization members will be able to edit the name and description, and will be able to activate or deactivate the auto-launch option for workflows that you create. They will also be able to view the details of the workflow, and clone it to a new draft.