Skip to main content

Collaboration & versions

Ways to collaborate on a workflow and stay safe as it evolves.


Collaborate on a workflow​

Workflows are shared through projects. Add people to the project a workflow lives in and every member sees the project's workflows; their project role (Viewer, Editor or Admin) governs whether they can run or edit them. See Projects.

There is no separate option to share a single workflow with one person. To bring someone in, add them to the project (or make a copy of the workflow in a project they belong to).

Who pays when a workflow is shared

Access doesn't change billing. Whoever runs a workflow bears the usage cost for that run. See Sharing and cost.


Export & import​

You can move a workflow between workspaces, or back it up, as a file.

  • Export as JSON — download the workflow's design from the toolbar menu: its nodes, edges, node settings, and the inputs you've written.
  • Import — load an exported workflow file to recreate it. You become the owner of the imported copy.
Your data doesn't travel with the export

An export carries the design, not the content. Attached Knowledge — files and web links — is deliberately left out, because it belongs to your workspace rather than to the workflow. Past runs, artifacts, and run history are left out too.

So after importing, open the Knowledge tab and re-attach the data the workflow needs. Until you do, it has nothing to work from.

Exports are tamper-protected

Every exported workflow is cryptographically signed, and JobKred verifies that signature on import, so you can only import genuine, unmodified files. An import must also be under 50 MB, with at most 100 nodes and 500 edges.


Make a copy​

Need a variation? On the Workflows list, open a workflow card's menu and choose Make a copy. Give the copy a name and pick the project it goes to: your personal project, or any project where you can create workflows. You get an independent copy you can change without touching the original. It's handy for trying a different approach or adapting a process for another department.

You can copy any workflow you can see in a project you belong to.

  • The copy is yours. The people who can see the original don't get access to it.
  • Copying into the same project keeps the workflow's Knowledge as it is, including the knowledge each node picked.
  • Copying into another project copies the workflow and its settings but not its Knowledge files, so add them again in the copy.
  • Not copied: schedules, run history and artifacts. The copy starts as a draft.

This is the same idea as copying a template, except the original is one of your own workflows rather than one of JobKred's starters.


Versions​

Workflows keep a version history in the Activities tab. As you make changes, JobKred snapshots the workflow, so you can review what changed between two versions and restore an earlier one if a change didn't work out — experimenting is always safe.

Two things to know:

  • Only the workflow's owner can restore a version.
  • If a colleague edited the workflow while you were browsing its history, the restore is refused rather than silently overwriting their work. Reopen the tab and try again.

While the Activities tab is open, editing is paused so browsing history can't disturb the current version — switch back to the Workflow tab to carry on building.


Next step​

Browse the specialists you can add as nodes → Agent Catalog.