How do users create a Live View?

Users can run /view or describe the desired output in Operations. Pilot generates the requested table, board, or chart from workspace records and schema fields. The result can be pinned so teammates can open it later from the Views hub.

Are Live Views static exports?

No. Live Views are intended as active surfaces connected to workspace data. Teams use them for ongoing reviews and can regenerate or adjust outputs in Operations when requirements change. This avoids stale spreadsheet snapshots and duplicate report maintenance.

Can different teams share the same view?

Yes. Pinned views are available through the Views hub for teammates with appropriate access. This supports shared pipeline and operations rituals, where everyone references the same output rather than separate personal builds with inconsistent filters or assumptions.

What if schema fields change over time?

Because views are tied to workspace schema, teams can regenerate them from Operations using updated object and field definitions. This keeps reporting aligned with the current model and reduces long-term drift between operational data structure and team decision surfaces.

Pin tables, charts, and boards

Create live reporting surfaces directly from Operations. Ask Pilot for a table, chart, or board, pin the result, and share it through the Views hub so teammates can work from current data instead of static exports.

12%

Forecast lift

Teams report cleaner pipeline reviews

Weekly CSV exports

When standups run from pinned views

<1m

View creation

From /view or natural language

Questions become shared surfaces

Generate, pin, and reopen Live Views from Operations.

Live Views turns operational questions into reusable team assets. A user can ask for a stage-based pipeline board or a quarter chart, then pin that output so others can open the same view later without rebuilding logic from scratch.

Because views are generated from workspace records and schema fields, they stay aligned with real data structures. Teams review status in shared surfaces and return to Operations when they need to adjust criteria, refine layout, or generate a new perspective.

Generate from conversation
Use /view or a natural-language request to create a live table, chart, or board from current records.
Pin once, reuse across team
Pinned views appear in the Views hub so teammates open shared outputs without rebuilding reports.
Anchored to workspace model
Views use your object and field definitions, keeping visualizations aligned with configured schema changes.

Generation

From request to working view in one flow

Generate live tables, boards, or charts directly from operational requests.

Run /view without leaving active work thread
Turn ad hoc questions into reusable assets quickly
Keep reporting tied to current workspace records

Reuse

Shared hub for recurring decision views

Pin views once, then share them from one hub across teams.

Reuse outputs in weekly standups and reviews
Avoid rebuilding filters for recurring meetings
Keep team discussion on one shared source

Alignment

Useful formats for different workflows

Choose table, board, or chart format based on decision workflow needs.

Inspect record detail in sortable tables
Track stage movement in board layouts
Monitor trends quickly through chart snapshots

Iteration

Schema-connected output that stays relevant

View outputs stay aligned with current object and field definitions.

Reflect custom schema instead of hardcoded models
Regenerate views after Setup changes
Reduce drift between data structure and reporting

Handoff

Operational loop between Views and Operations

Inspect in Views, then act in Operations without losing context.

Move from insight to updates in same workspace
Follow up on stalled records immediately
Keep decision trail connected to executed actions

Questions

Short answers before you request access.

How do users create a Live View?: Users can run /view or describe the desired output in Operations. Pilot generates the requested table, board, or chart from workspace records and schema fields. The result can be pinned so teammates can open it later from the Views hub.
Are Live Views static exports?: No. Live Views are intended as active surfaces connected to workspace data. Teams use them for ongoing reviews and can regenerate or adjust outputs in Operations when requirements change. This avoids stale spreadsheet snapshots and duplicate report maintenance.
Can different teams share the same view?: Yes. Pinned views are available through the Views hub for teammates with appropriate access. This supports shared pipeline and operations rituals, where everyone references the same output rather than separate personal builds with inconsistent filters or assumptions.
What if schema fields change over time?: Because views are tied to workspace schema, teams can regenerate them from Operations using updated object and field definitions. This keeps reporting aligned with the current model and reduces long-term drift between operational data structure and team decision surfaces.