Browse and connect

Review records imported from business tools

An imported record is information copied or interpreted from another system, such as a customer note or contact update. A proposed record may need a person to check it before it becomes current information in your Mind. This guide helps you compare an import with its source and avoid treating a successful capture as a verified business fact.

Contents

Establish what produced the record

Open the original source and the saved capture or proposed change. Check the external account, document or item, its date, the importing app and the intended destination. Preserve a stable source reference so another authorised person can repeat your check.

Some source packages, including Records Engine and Web Enricher, can prepare structured records or review batches. They were source candidates rather than entries in this guide’s selected catalog. Do not assume their workflow is installed because an example or old instruction names it. Check available extensions and the actual installed app first.

Compare identity, meaning and date

Make sure the record refers to the intended company, person or transaction. Similar names are not enough. Check dates, units, ownership and status against the source. If the app has combined several items, verify that each source supports the particular claim assigned to it.

A public web result can support a sourced observation; it does not prove a private commercial commitment. When evidence is incomplete, keep the uncertainty visible or leave the proposed fact out. Do not fill a missing field from a similar record.

Decide the actual proposed change

Read the complete proposed difference and its reason. Check whether the result is a new evidence record, a correction to current information or a replacement operating record. Those have different consequences. Follow reviewing changes for the approval and source readback.

If an installed app presents a review batch, use its supported batch controls and inspect the outcome for every item you decide. A partially loaded page or failed item does not establish that the rest succeeded. Keep references to unresolved items before leaving the page.

Correct an import without losing its origin

Name the incorrect field, the correct value and the evidence for it. Preserve the source and unrelated content. Correcting saved information explains how to check whether the correction saved immediately or still needs review.

If the source system itself is wrong, decide where the authoritative correction belongs. Editing a Mind copy does not update the external application. If the importer later repeats the incorrect value, pause the affected work and have the authorised maintainer fix the source or mapping before accepting another batch.

Related

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Review records imported from business tools

Apps, sensors and connectors · Browse and connect · [How it works](https://app.mensara.ai/how-it-works)

An imported record is information copied or interpreted from another system, such as a customer note or contact update. A proposed record may need a person to check it before it becomes current information in your Mind. This guide helps you compare an import with its source and avoid treating a successful capture as a verified business fact.

[Page as Markdown](https://app.mensara.ai/how-it-works/imported-records.md)

## Establish what produced the record

Open the original source and the saved capture or proposed change. Check the external account, document or item, its date, the importing app and the intended destination. Preserve a stable source reference so another authorised person can repeat your check.

Some source packages, including Records Engine and Web Enricher, can prepare structured records or review batches. They were source candidates rather than entries in this guide’s selected catalog. Do not assume their workflow is installed because an example or old instruction names it. Check [available extensions](https://app.mensara.ai/how-it-works/apps-sensors-connectors) and the actual installed app first.

## Compare identity, meaning and date

Make sure the record refers to the intended company, person or transaction. Similar names are not enough. Check dates, units, ownership and status against the source. If the app has combined several items, verify that each source supports the particular claim assigned to it.

A public web result can support a sourced observation; it does not prove a private commercial commitment. When evidence is incomplete, keep the uncertainty visible or leave the proposed fact out. Do not fill a missing field from a similar record.

## Decide the actual proposed change

Read the complete proposed difference and its reason. Check whether the result is a new evidence record, a correction to current information or a replacement operating record. Those have different consequences. Follow [reviewing changes](https://app.mensara.ai/how-it-works/changes-approvals-receipts#review-one-proposal) for the approval and source readback.

If an installed app presents a review batch, use its supported batch controls and inspect the outcome for every item you decide. A partially loaded page or failed item does not establish that the rest succeeded. Keep references to unresolved items before leaving the page.

## Correct an import without losing its origin

Name the incorrect field, the correct value and the evidence for it. Preserve the source and unrelated content. [Correcting saved information](https://app.mensara.ai/how-it-works/suggest-a-correction) explains how to check whether the correction saved immediately or still needs review.

If the source system itself is wrong, decide where the authoritative correction belongs. Editing a Mind copy does not update the external application. If the importer later repeats the incorrect value, pause the affected work and have the authorised maintainer fix the source or mapping before accepting another batch.

## Related

- [Bring email, calendar events and files into your Mind](https://app.mensara.ai/how-it-works/connections-and-capture)
- [Review changes and check what was saved](https://app.mensara.ai/how-it-works/changes-approvals-receipts)
- [Ask what is current, then ask why](https://app.mensara.ai/how-it-works/current-and-evidence)
- [Recover pending, failed or interrupted work](https://app.mensara.ai/how-it-works/interrupted-work)

Previous page: [Plan SharePoint capture and export for your Mind](https://app.mensara.ai/how-it-works/sharepoint)

Next page: [Build and publish a team View](https://app.mensara.ai/how-it-works/build-a-team-view)

A View is a small web page on your Mensara Mind that presents saved records as a board, table or dashboard.

[Join the waitlist](https://app.mensara.ai/#waitlist)