What is allowed to leave the team

This page shows the sharing rule in one view. A status and a short summary can be shared outside the team. The controlled files stay protected in your own systems. A quality reviewer approves before anything is shared.
What gets shared A status and a short summary can be shared. Controlled files stay protected in your own systems. A reviewer approves first. Candidate workspace, mock data only.

For example: a supplier asks if a part is qualified. You can confirm the status and send a short summary. The controlled drawing never leaves your own systems, and a quality reviewer signs off before the answer goes out.

Shared versus protected

Each item on the left sends only its status and summary across the review line to a reviewer. The controlled file beside it stays protected and never crosses. Hover or tap any item to see what it is, who owns it, and what stays protected.

What can we share?

0 Items in view
0 Ready to share
0 Held for review
Can be shared
  • Source type and status
  • Whether evidence is linked, the status only
  • Owner role and approval state
  • The open question
  • Where it could fall short
  • A link back to the source
Stays protected
  • No CAD and engineering models
  • No CUI and confidential documents
  • No ITAR and export-controlled content
  • The contents of any controlled file
  • Supplier names and part numbers
  • Network layout and live systems

What you are seeing

The map draws the real work items for the department you picked in the "Viewing as" control. Colored markers carry only the status and a short summary across the review line to a reviewer. The controlled file stays behind the line and is never shared. Switch the department to see a different team's split.

Sample shape only. The live workspace reads only the status and summary from your own system. Nothing here is a real file.

The rule in one line

  • Status and summary only crosses the review line: the item label, its status, the open question.
  • Controlled files stay protected in your own system. The file contents never leave it.
  • A person decides what reaches the readiness packet.