---
title: "Commit territory changes"
slug: "commit-territory-changes"
description: "How do you commit territory changes in Fullcast so they export to your CRM, and how do you confirm a change committed?"
updated: 2026-08-11T21:54:43Z
published: 2026-08-11T21:54:43Z
canonical: "support.fullcast.com/commit-territory-changes"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.fullcast.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Commit territory changes

Committing a change finalizes it in Fullcast and queues it to export to your CRM on the next scheduled export job. Until you commit, a change stays proposed — staged in Fullcast and marked with a **yellow dot** — and doesn't export. For what proposed and committed mean and how the Current, Proposed, and Difference change states relate, see the [**Current, Proposed, and Difference views**](/plan-and-pay/docs/current-proposed-and-difference-views) article.

## Before you begin

- If you changed territory rules, rerun the rules at the hierarchy level where you made the change before you commit. If you don't, those rule changes won't be included in the commit.

## Commit changes

You can commit from the territory hierarchy or from the account grid.

> [!WARNING]
> Warning
> 
> Committing is not reversible with **Undo**. Undo only discards proposed changes; to reverse a committed change, make a new change and commit it.

### From the territory hierarchy

1. In the territory hierarchy, select the level you want to commit — select **All Companies** (the top level) to commit every change in the plan, or a lower node to commit that node and the levels beneath it.
2. Open the three-dot menu for that level.
3. Select **Commit**.

### From the account grid

1. In the account grid, select the accounts you want to commit.

> [!NOTE]
> Note
> 
> To select several accounts, use the row checkboxes, or click the first account and hold `Shift` while you click the last to select a range.
2. Click the **Actions** (wrench) button.
3. Select **Commit**.
4. In the confirmation window, type `CONFIRM` and click **Confirm**.

## Verify a change committed

After committing, confirm it took:

- The **yellow dot** clears once every change on a node is committed. If you commit only some accounts on a node, the dot stays until the rest are committed.
- Switch to the **Current** change state — your change now appears there. Right after a commit, the **Current** and **Proposed** change states match, and the **Difference** change state shows nothing for that change.
- Check the **Committed On** field in the grid for the date and time of the commit.
- Check the **Modified By** field to see who committed it.
- If you have audit access, open the audit log and look for the tree-hierarchy commit record.

![Audit log entries showing tree hierarchy commit records](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(432).png)

##

## Related

- [Current, Proposed, and Difference views](/current-proposed-and-difference-views.md)
- [Move accounts from node to node](/how-to-move-accounts-from-node-to-node.md)