Skip to main content
Version: 2026.08

Lineage

Lineage shows how a model or artifact was produced and what it was used to produce. Parent/child relationships are recorded automatically when jobs run: outputs are linked to the input files they consumed.

Use lineage to answer questions like:

  • Which design files and simulation results led to this part?
  • For a multi-step workflow, what did each step produce and which downstream steps consumed it?

Concepts​

  • Parent — a resource that was used to generate another resource.
  • Child — a resource that was generated from another resource.
  • Lineage graph — the parent/child relationships from the selected resource, in both directions.

View lineage for a resource​

  1. Open any model or artifact on the Files page (or from a System Resource tree).
  2. In the center panel header, open the Lineage tab.
  3. The graph centers on the selected resource and expands outward:
    • Parents are shown upstream of the resource.
    • Children are shown downstream of the resource.
  4. Click any node to navigate to that resource. From there you can open its Lineage tab to continue exploring.

Required role: Viewer or above.

Lineage and jobs​

When a job completes, its output resources are automatically related to the job's input files. Workflows build lineage without extra steps:

  • Run a job — outputs are linked to inputs.
  • Chain jobs together — each step's outputs become parents of the next step's outputs.
  • Open any resource's Lineage tab to see the execution graph that produced it.

See Jobs and Automation for running and reviewing jobs.

Sharing and lineage​

Collaborators with access to the underlying resources see the same lineage you do. File-level permissions still apply — users without access to a particular resource see it in the graph with limited information.

See Sharing and Access Control for sharing details.