How Signals become Lenses
Signals are the information available inside a Unit. Lenses are the shared insights Orbit synthesizes from those signals. What counts as a signal A signal can come from: A description or status change A Thread message or poll An Attachment A Relationship or dependency A time entry or estimate A Document or Diagram A meeting recording, transcript, or note A connected source item A supported provider comment from Jira, Azure DevOps, Linear, monday.com, or Wrike What a LFew readersExplore Lenses
Use Lenses to review shared insights and the Map to trace them to source signals. Browse Lenses Open the relevant Unit. Select Ask Orbit. In Orbit's side rail, select Lenses. Search, or filter with All and the Lens category chips. Sort by Recent or Oldest. Open a Lens to review its content, supporting signals, and actions. The header shows the total Lens count and how many sources were synthesized. Use the Lens Map Open the Lens Map to see how sigFew readersTurn a Lens into action
Open a Lens when an insight needs follow-up. Available actions From a Lens you can: Ask Orbit about the insight Push it to a supported work provider Mark it resolved or unresolved Schedule meeting Remove the Lens Push a work item Select Push. Choose a connected provider and destination. Review the suggested title and deFew readers