Local data

Keep original files local and understand each connected action.

What this is for

Use this guide to decide where the data stays and what a connected feature sends. Local operation and cloud-model access are separate parts of the workflow.

Local direct tools

Action	Where it runs
Read the configured copied batch	Local files and local code.
Inspect a selected folder	The local browser.
Preview and save a supported CSV	The local workspace.
Compare supported terms	Local comparison functions.
Save a desktop result	Local run storage.
Generate desktop PDF or HTML	Local saved result; PDF uses Chrome.

Connected AI

When AI assistance is enabled, request text and the selected buyer or run identifier can go to the configured provider. The routing step does not automatically send the entire batch. Content pasted into a request is part of that request. Provider access and data policies apply to the connected step.

Web workspace

The web product has its own calculation source and agent path. Its current reports live in the browser that created them. Desktop and web state are not automatically synchronized.

Source identity

Keep the dataset ID, version, date, units, and original reference with a result. A new import or run date does not update the source’s as-of date. Matching totals are not proof that two sources contain the same assets.

Public examples

Published guides use a fictional fund and a $4 billion example portfolio. These figures are documentation examples, not a disclosure of the active workspace or a statement of assets under management.

Team controls

Local approval is not company SSO. Live integrations, managed team permissions, and hosted recipient access need their own enabled configuration. Read the status shown on each integration guide.