Versions & Sharing

Track every change with version history, compare differences between versions, restore previous states, and share workflows with your team.

Version History

Every time you save a workflow, A91I creates a new version. The version history records the complete state of the workflow — all nodes, edges, positions, configurations, and trigger settings.

This means you can always go back to any previous save point, compare what changed, and understand the evolution of the workflow over time.

Viewing Version History

Open the workflow

Navigate to the workflow you want to inspect.

Open version history

Click the version history icon in the editor toolbar (clock icon). A panel shows all saved versions, newest first.

Browse versions

Each version entry shows the version number, save timestamp, and who made the change. Click a version to preview it.

Comparing Versions

Select two versions and click Compare to see a side-by-side diff. The comparison shows:

Nodes added — new nodes that appear in the newer version.
Nodes removed — nodes that were deleted.
Nodes modified — nodes with changed configurations, positions, or connections.
Edge changes — new or removed connections between nodes.
Configuration changes — field-by-field diff of node parameters.

The diff view uses color coding: green for additions, red for removals, and yellow for modifications.

To restore a previous version, open the version history panel, click the version you want, and click Restore This Version. The workflow reverts to that state. This creates a new version entry (it does not delete the versions in between), so the restore itself is tracked in history.

Non-destructive

Restoring a version never deletes history. You can always go forward again to a more recent version if needed.

Cloning Workflows

Clone a workflow to create an independent copy. The clone gets a new ID and name (suffixed with "(Copy)") but retains all nodes, edges, and configurations. Changes to the clone do not affect the original.

Cloning is useful for:

Creating variations — clone a working workflow and modify it for a different use case.
Safe experimentation — clone before making risky changes. If the experiment fails, delete the clone.
Template creation — build a standard workflow, then clone it for each team or client.

Sharing Workflows

By default, workflows are private to the user who created them. Sharing lets other organization members view, edit, or run the workflow.

Permission Levels

Level	View	Edit	Execute	Delete
View	Yes	No	No	No
Edit	Yes	Yes	Yes	No
Execute	Yes	No	Yes	No
Admin	Yes	Yes	Yes	Yes

View: See the workflow structure and execution history. Cannot modify anything.
Edit: Full editing access — can change nodes, configurations, and trigger settings. Can also run the workflow.
Execute: Can trigger test runs and view results, but cannot modify the workflow structure.
Admin: Full control, including the ability to delete the workflow, modify sharing settings, and manage versions.

Workflow Visibility

In addition to user-level sharing, workflows have a visibility setting:

Private: Only the creator and explicitly shared users can access the workflow.
Team: All members of the organization can view the workflow. Edit and execute permissions still require explicit sharing.

Team Collaboration

Best Practices

Name workflows descriptively so team members can find them easily.
Add descriptions explaining what the workflow does and when it runs.
Use version history to understand changes made by other team members.
Share with the minimum required permission level — View for observers, Edit for co-builders.
Clone before making major changes to a shared workflow. Merge the changes back after testing.
Use node groups to organize complex workflows so collaborators can understand the structure at a glance.

Change Tracking

All workflow changes are tracked in the organization's audit log. The audit log records who changed what, when, and the before/after values. Navigate to Settings → Audit Log to browse the full history.