Data actions

Review and run the account changes Kernel recommends for your CRM

Data actions is where you review the account changes Kernel recommends for your CRM. The queues cover Create accounts, Associate accounts, Delete accounts, and Merge accounts. The queues available to you depend on your workspace configuration. A recommendation does not change your CRM on its own.

Set the rules

Open Data actions > Rules to choose which recommendations Kernel creates and how it handles protected accounts and related records.

Rules tab	What you choose
Duplicates	How to handle duplicate records and the Absorbed special case.
Related objects	Which related records to back up and whether to delete them before removing an account.
Associations	Which parent suggestions to skip.
Deletions	Which accounts to mark for deletion and which protections to apply.
Merges	Whether merge actions can include safeguarded accounts.

Read the cleaning rules guide

Saving rules changes the configuration. Refresh the recommendations after a rule change, then review the updated queues.

Choose an action

Queue	What it does
Create accounts	Add accounts missing from your write source using your configured field mappings.
Associate accounts	Link an account to an existing parent, correct its parent, or create a missing parent.
Delete accounts	Remove accounts that match your deletion rules.
Merge accounts	Combine duplicates into a primary account.

Each queue has an Actionable view for recommendations awaiting a decision or execution, and an Actioned view for completed or rejected recommendations.

Review and run

Open a recommendation and check the proposed change, its reasoning, risk tier, and CRM fields. Confirm the parent for an association, the record to remove for a deletion, or the primary record for a merge.

Choose Create, Associate, Delete, or Merge to review the confirmation and queue the change. Choose Reject to move a recommendation to Actioned without changing the CRM. You can act on one recommendation or a selected group.

Safeguarded accounts are excluded from association and deletion by default. In a merge, safeguarded duplicates are kept separate by default; a safeguarded primary can still receive field updates. Each action has its own Allow … safeguarded accounts setting on the Rules page. The confirmation shows the records included in the action and any protected records that will be skipped.