Skip to content

Notebooks And Sharing

A notebook captures more than text notes. It persists:

  • lot and snapshot context
  • active test focus
  • selection state
  • scenario limits
  • spatial analysis pushes
  • chart and modal-driven what-if conclusions

A saved notebook can carry the current lot, selection, and what-if context into scoped SQL work.

Notebook saves now track base_version.

That means version history can tell the difference between:

  • a normal save from the previous head
  • a valid save that was made from stale notebook state

This does not block saves. It makes lineage visible.

Use personal spaces for private work and shared spaces for team workflows.

Shared spaces have explicit access management and separate notebook share links.

Notebook share links are read-only.

That is true even if the owner can still edit the notebook.

The product also caps active share links per notebook.

Saved notebooks can now move through document lifecycle states:

  • active
  • archived
  • controlled

Think of them as:

  • active: working analysis
  • archived: not part of active collaboration
  • controlled: frozen artifact

Use controlled when a notebook should remain shareable but no longer editable in place.