Onshape Documents are a powerful organizational tool. Think of Onshape Documents as containers for project-related data (Parts, Assemblies, Drawings, etc.). Consider limiting the number of Tabs in any one Document to 40 or fewer. As portions of your design mature, you can move those Tabs into their own Documents. Note that you can store non-CAD information, such as photos, videos or PDFs in a Document as well.
Interrelated Part Studios and Assemblies that are defined in the same Document will update automatically.
When a product is defined in multiple Documents, make links (or references) from objects in one Document to objects in a Version in another. You control when they update. This prevents the assembly corruption issues seen in file-based CAD systems.
Part Studios are for defining the shapes of parts, NOT for defining Assemblies. Most Part Studios will define 1 to 7 unique parts with fewer than 200 features.
A Version is a named and immutable checkpoint of your Document. All Tabs in that Document are versioned together. Use Versions whenever possible. Versions are not meant to be used for Release Management. If formal Release Management is an important part of your design process, it is highly recommended that you subscribe to Onshape Professional or Onshape Enterprise.
Restore from the Document history to reflect any prior state of your Document. This restores all actions by all users across all Tabs of the Document.
When possible, avoid aesthetic features like fully realized threads or knurls, and complex embossed text or symbols.