Views

Views are calculated presentations of Project data. The View pane supports Table, Onepager, and Timeline. A saved View stores a named configuration so authorized members can reopen the same arrangement; it does not freeze a copy of the business data.

Use Pivot tables for Table configuration, Onepager for the canvas, and Timeline for time-based series. The Resources pane's authoring Table mode is a different tool and is not a saved calculated View.

Access and shared configuration

Saved Views belong to the Project and are shared with authorized readers. Analyst ownership limits who may modify a configuration; it does not make that View a private personal workspace. There is no per-View sharing dialog or separate Viewer invitation in the current pane. Manage Project and Layer access through Workspace and Layers.

Controls being visible is not proof that your role can persist the action. Saves and deletions are permission-checked. A Layer-only Editor may perform supported contextual data edits, but does not thereby gain Project-wide saved-View administration or assistant access.

Default and temporary configuration

Every opened Project workspace starts with a built-in Default Table View. Default is a temporary starting configuration, not a saved record owned by a member. It has no name editor or Save view button. Configure it for exploration, then use Add view to keep that configuration under a name.

There is no Make default control and no user-selected replacement for the built-in starting View. You cannot rename or delete Default. Selecting a saved View makes it active now, but does not set a persistent startup preference.

Changes to the current configuration, filters, date, or name are drafts until you explicitly save them. Switching away and back reloads the stored configuration and can discard unsaved work. Reopening the workspace is not a draft-recovery workflow. Another member's saved update can also reload the active saved configuration. Save deliberately before navigating away.

Merely configuring a View changes its presentation, not the source data. Explicit data-editing actions, such as writable Onepager reference drops, are separate writes and follow their own permissions and Undo behavior.

Create a saved View

Prerequisite: Analyst or higher Project access.

1. Open the Project's View pane. Show the pane again through the workspace pane controls if it is hidden.
2. Select Add view.
3. Enter a nonempty View name, such as Product overview for the fictional Product Atlas dataset.
4. Choose Table, Onepager, or Timeline in Type. The dialog starts with Table each time; it does not automatically adopt the type you were viewing.
5. Select Add view and wait for the write to complete.

The new saved View appears in the selector and becomes active after successful creation. The dialog closing is not, by itself, proof that creation succeeded; check the selected View and any action error.

When the chosen type matches the currently selected View, creation copies its current configuration, including unsaved configuration edits. This is also how you save an explored Default Table as a new View or create a same-type variation. It does not change the original saved View.

When the chosen type differs, creation starts with that type's initial configuration. It does not convert a Table into a Onepager or Timeline. Configure the new type using its dedicated article, then save. An empty Table requires rows, columns, and displayed cell content before it can calculate a result; creating its name alone does not populate it.

To copy a Onepager or Timeline, select the source first, then explicitly choose that same type in Add view. Leaving the dialog on Table creates a Table instead of copying the canvas or series.

Select and configure a View

1. Choose an entry from the View selector at the top of the View pane.
2. Confirm its name and type-specific controls.
3. Adjust the configuration in that module.
4. Wait for the calculated result to finish updating before interpreting it.

Only the selected type calculates an active result. Switching to another View does not keep showing an obsolete result from the previous identity. An unconfigured View or a filter with no matches can produce an empty state; that is not proof that Project data is missing.

Selecting or configuring the View does not change which Resources mode you are using. The authoring grid and the saved calculated View can have different purposes and state.

Filter, date, and Layer context

Use the View's filter control to open View filters. Build a complete rule, then select Apply filters. Clear filters removes the View filter from the current draft. These filter changes recalculate the current presentation; use Save view to retain them in a saved View.

Filters use the same Class and property rules described in Conditions. They select calculated contexts and results; they do not create condition overrides on source fields.

Set As of date to evaluate data at a particular date. With no explicit date, evaluation uses the current date. This date is part of the View configuration, not an instruction to create or change a snapshot. Timeline series can also evaluate historical values across a range; follow Timeline historical evaluation for those distinctions.

The active Layer is additional workspace context and is not stored in the saved View. View results combine the current Layer with the View's own filter. Onepager box filters and Timeline series filters may narrow the result further. Saving a View while Northland market is active does not pin it permanently to Northland.

For repeatable review, identify the saved View, date, and active Layer together. Two people opening the same configuration may see different results because of their authorized scope, selected Layer, current data, or an unspecified date advancing to today. A saved View is not an immutable export or access grant.

The Product Atlas demonstration names its saved presentations Market prices and Feature matrix (Table), Launch brief (Onepager), and Release roadmap (Timeline). Their configured As of date is 2026-10-01. The demo is not automatically installed in your account. The Product overview creation example above is an additional practice View.

Save and rename

1. Select the saved View you are allowed to manage.
2. Make configuration changes as needed.
3. To rename it, edit View name in the pane header. A blank or space-only name cannot be saved.
4. Select Save view and wait for successful completion.
5. Reopen the View to confirm the saved name and configuration.

Save persists both the current name and the current configuration. Renaming is not a name-only operation: other unsaved configuration edits are included in the same save. Use Add view with the same type when you intend a separate variation instead of changing the shared original.

The Table action Save current sort to this View also saves the current View configuration; it is not available for the temporary Default. It may include other current configuration edits along with the sort.

Saved changes become available to other authorized members. If someone has changed the View since you loaded it, the save can be refused rather than silently overwriting their work. Refresh, inspect the latest configuration, and deliberately reapply your edits. Do not repeatedly submit a stale draft.

There is no ordinary pane control to change an existing View's type, reorder the saved list, or choose a custom startup default. Create a new View of another type rather than expecting an in-place conversion.

Delete a saved View

The ordinary View pane currently has no Delete view button or management menu. Do not look for deletion in the Add view dialog, and do not delete resources to remove a presentation.

Deleting a saved View is supported through the enabled AI assistant, subject to current Project permissions and command validation:

1. Identify the Project and the exact saved View. Use an unambiguous name and type when names are similar.
2. Ask to delete only that saved View, not its resources, properties, or source data.
3. Review the proposed action and any approval request before allowing deletion.
4. Check the completion result and the View selector.

Analysts can delete their own saved Views; Editors and higher can manage others. The assistant may be disabled or unavailable for your account, so this is not a universal replacement for a missing UI button. A small eligible action may run without a separate approval dialog; follow assistant approval behavior.

Deleting the saved configuration does not delete the underlying business data. If the selected saved View disappears, the workspace falls back to Default. Default itself is not a deletable saved View. Do not assume deletion has a recoverable receipt; see Undo limitations.

Refreshing and troubleshooting

When data changes, active results refresh. While the current calculation is updating, the last completed result may remain visible and some configuration or editing interactions are unavailable. Wait for completion before treating a displayed result as current. A View save, a source-data save, and a completed calculation are distinct events.

No private-View sharing toggle, public anonymous View link, View export workflow, or type conversion control is provided by this pane. See Troubleshooting for connection failures, and the dedicated presentation articles for module-specific limits.