# Reset

{/* AUTO-SYNCED SOURCE: this page lives in apps/app/src/modules/db-leads/docs/ and is mirrored into the docs app by `bun sync:module-docs`. Edit it in the module, not in apps/docs. */}

<Lead>
Sometimes you want to start over: after a larger change to the qualification, after a scan with badly tuned signals, or when you point the tool at a different onOffice account. The **Maintenance** area in the settings (group Other) does exactly that. It lives there because it holds everything you rarely or never need and only find when you go looking for it.
</Lead>

## The dividing line

<Callout tone="warning" title="What the tool computed goes. What it fetched stays.">
Contacts and activities **mirror your CRM**: they are here because they are there. Deleting them here corrects nothing, it only smashes the mirror, and the next sync brings everything back unchanged. In between there is a state where the list is empty and nobody can tell whether that was a bug.
</Callout>

There is therefore **no** action here that deletes contacts or activities, and there never should be. If you genuinely want contacts gone, there are two proper paths: archive them individually, or disconnect from the CRM. Both live elsewhere and are named after what they do.

## The four scopes

<DefinitionList>
  <DefItem term="Findings">Deletes the findings from the inbox. The briefings stay on the contacts. The right move after a scan that ran with the wrong sensitivity.</DefItem>
  <DefItem term="Assessments">Clears briefings, signals, sales readiness and scores on the contacts. The next scan recreates them. The right move after changing the qualification parameters.</DefItem>
  <DefItem term="Pipeline">Clears phase assignment and manual decisions (scan exclusion, archive). The right move after recutting the pipeline.</DefItem>
  <DefItem term="Fresh connect">All of the above plus the sync run logs. The right move when the tool should point at a different onOffice account.</DefItem>
</DefinitionList>

## What else lives under „Maintenance"

Two actions where **nothing is lost**. They only take time, which is why they
sit here and not where you click every day.

<DefinitionList>
  <DefItem term="Full scan">Re-analyses every contact in the time window, including the ones that have not changed, and uses up one run from your monthly allowance. It used to sit next to the regular database scan; two buttons side by side, one of which costs a multiple of the other, are a trap. The allowance now shows right on the card.</DefItem>
  <DefItem term="Complete synchronisation">Reads your entire book from onOffice again, from the start. On a grown book that takes hours. You only need it when something went wrong during a sync and the data no longer lines up. The regular sync only fetches what changed since last time and is done in seconds.</DefItem>
</DefinitionList>

Both ask first and show you what will happen. Neither asks you to type
anything: only the actions further up do that, because only there does
something actually disappear.

## What happens to property leads

Entries **from the analysis** disappear together with the assessments, because they are their output. Entries you **added or confirmed yourself** stay: they are your work, not the scan's. See [Ownership](/tools/db-leads/objekte).

## Who may do this

The workspace **owner** only, or whoever has explicitly been granted the **Reset DB-Leads** permission (`tools.danger.db-leads`). It is preset for no role. See [Permissions](/tools/db-leads/berechtigungen).

## Before you reset

<Checklist>
  <ChecklistItem>The dialog names how much will disappear. Read it before confirming.</ChecklistItem>
  <ChecklistItem>If you need the findings as evidence, export them as CSV first. See [List, filters and export](/tools/db-leads/liste-filter-export).</ChecklistItem>
  <ChecklistItem>A reset cannot be undone. Assessments are recreated by the next scan, but that costs AI budget again.</ChecklistItem>
</Checklist>

The reset is written to the workspace audit log with its counts.

## Further reading

<CardGrid>
  <Card title="Permissions" href="/tools/db-leads/berechtigungen">Who can hold this permission.</Card>
  <Card title="Database scan" href="/tools/db-leads/datenbank-scan">What gets recreated afterwards.</Card>
  <Card title="Settings" href="/tools/db-leads/einstellungen">The parameters you are resetting because of.</Card>
</CardGrid>