Skip to main content

Sharing & versions

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

Share a workflow​

As the owner, use Share to give colleagues in your company access. Search for people by name and add them; the workflow then appears under their Shared with me.

Who pays when a workflow is shared

Sharing grants access, not billing. Whoever runs a shared 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.

Duplicate​

Need a variation? On the Workflows list, use a workflow card's menu to Duplicate it. You get an independent copy you can change without touching the original — handy for trying an alternative approach or adapting one process for a different department.

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.