Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/TerritoryManagement/AssignAccts/RemoveFromTerr.htm

## Removing Accounts from Territories

End users can quickly remove accounts from their territory via a dedicated button on account detail pages. Selecting this button enables users to create a DCR that removes the account from their territory, which can include a reason for removal. The DCR can then be routed via customer-specific processes for additional review and approval.

**Who can use this feature?**

* End Users – Browser, iPad
* [Remove Accounts from Territories](#Removing)
* Users do not require an additional license

### Configuring Removing Accounts from Territories for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure this feature:

1. Ensure the following features are configured:

   * [Configuring Territory Management](../Config.htm)
   * [Configuring Data Change Requests](../../Integration/Network_Integration/Configuration/DCR_Configuration.htm)
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | data\_change\_request\_\_v | CRE | remove\_from\_territory\_\_v | * account\_\_v * challenge\_reason\_\_v * territory\_\_v * territory\_label\_\_v * data\_change\_request\_status\_\_v * external\_status\_\_v * sent\_datetime\_\_v * network\_customer\_master\_mode\_\_v | Edit |
6. Navigate to the **account\_\_v** object in the permission set.
7. Grant Execute access to the **Remove from Territory** action.
8. Navigate to **Admin > Configuration > Objects > account\_\_v > Object Types > Actions**.
9. Add the **Remove from Territory** action to the appropriate object types.
10. Navigate to **Business Admin > Objects > Veeva Settings > Global Veeva Settings**.
11. Populate the **data\_change\_request\_mode\_\_v** Veeva Setting with the appropriate value:

    * 1 – Enables users to create [DCRs](../../Integration/Network_Integration/Data_Change_Requests/Editing_DCRs.htm)
    * 2 – Select this option if [Creating Unverified Records](../../Integration/Network_Integration/Data_Change_Requests/CreatingUnverifiedRecords.htm) is also enabled

    Do not populate this setting with 0. This prevents users from creating DCRs regardless of other object permissions, which is not supported with this feature.
12. Populate the REMOVE\_FROM\_TERRITORY\_DCR\_ACCT\_TYPES\_\_v Veeva Setting with **REMOVE\_FROM\_TERRITORY\_DCR\_ACCT\_TYPES;;Feedback**
13. Navigate to **Business Admin > Objects > message\_\_v** and edit the following Veeva Messages in the Feedback category with the appropriate text: This is only required if admins want to update the messages from the default text.

    | Veeva Message | Displays | Default Text |
    | --- | --- | --- |
    | REMOVE\_FROM\_TERRITORY\_ACCEPTED\_RESOLUTION\_NOTE | In the resolution\_note\_\_v field of an approved Remove from Territory DCR. | Account successfully removed from territory. |
    | REMOVE\_FROM\_TERRITORY\_REJECTED\_RESOLUTION\_NOTE | In the resolution\_note\_\_v field of a rejected Remove from Territory DCR. | The request to remove the account from your territory has been rejected. |
    | REMOVE\_FROM\_TERRITORY\_WARNING | In the modal after users select the Remove from Territory button. | Removing this account can cause other related accounts to be removed from your territory. |

    See [Veeva Messages](../../Getting_Started/SettingUp/Veeva_Messages.htm) for best practices when editing Veeva Messages.
14. Edit the **REMOVE\_FROM\_TERRITORY\_DCR\_ACCT\_TYPES** Veeva Message in the Feedback category.
15. Populate the Text field with a double-semicolon separated list of account\_\_v object types that the Remove from Territory button displays. For example:

    professional\_\_v;;hospital\_\_v

#### Configuring Challenge Reasons

To enable end users to submit a reason for creating the DCR, place the challenge\_reasons\_\_v field on the appropriate data\_change\_request\_\_v layouts.

It is recommended that customers determine and implement an appropriate manual or automatic process that provides users with feedback on their request to remove an account from their territory.

#### Enabling Lifecycles on Data Change Requests

Admins can enable lifecycles on Remove from Territory Data Change Requests, providing workflow control beyond the limitations of standard DCR statuses of Submitted, Pending, and Processed. Enabling an object-specific lifecycle for DCRs allows for the definition of custom states for the approval process.

Enabling lifecycles is not recommended for DCRs managed by Veeva Network.

For details on configuring object lifecycles and enabling them for specific objects, see [Configuring Object Lifecycle States](https://platform.veevavault.help/en/gr/30683/).

### Removing an Account from a Territory as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

Browser
iPad

To remove an account from a territory in the Browser:

1. Navigate to the appropriate account.
2. Select the **All Actions** menu.

   ![](../../../Resources/Images/Accounts/TerritoryManagement/RemoveFromTerr.png)
3. Select **Remove From Territory**.

   An error displays if users select this button on an account they are not currently aligned to.
4. Select the appropriate values:

   * Territory – Select the appropriate territories to remove the account from if the account and user are assigned to multiple territories

     Separate DCRs are created for each selected territory.
   * Challenge Reason – Values available for selection are based on the values of the challenge\_reasons\_\_v picklist on the data\_change\_request\_\_v object

   ![](../../../Resources/Images/Accounts/TerritoryManagement/RemoveFromTerr1.png)
5. Select **Submit**.

To remove an account from a territory on the iPad:

1. Navigate to the appropriate account.
2. Select the **All Actions** menu.

   ![](../../../Resources/Images/Accounts/TerritoryManagement/RemoveFromTerr2.png)
3. Select **Remove From Territory**.

   An error displays if users select this button on an account they are not currently aligned to.
4. Select the appropriate values:

   * Territory – Select the appropriate territories to remove the account from if the account and user are assigned to multiple territories

     Separate DCRs are created for each selected territory.
   * Challenge Reason – Values available for selection are based on the values of the challenge\_reasons\_\_v picklist on the data\_change\_request\_\_v object

   ![](../../../Resources/Images/Accounts/TerritoryManagement/RemoveFromTerr3.png)
5. Select **Submit**.

Additionally, alerts are automatically generated to notify iPad users when their submitted removal requests are processed based on the values of the external\_status\_\_v and result\_\_v fields:

| external\_status\_\_v | result\_\_v | status\_\_v | Displays in My Alerts? |
| --- | --- | --- | --- |
| change\_pendingreview\_\_v | n/a | submitted\_\_v | Yes |
| change\_processed\_\_v | change\_accepted\_\_v | processed\_\_v | No |
| change\_processed\_\_v | change\_rejected\_\_v | processed\_\_v | Yes |

Created DCRs have an initial external\_status\_\_v field of change\_pendingreview\_\_v. Updating the result\_\_v field to change\_accepted\_\_v removes the account from the requesting user’s territory.

Only the Result field should be changed when approving the DCR. This triggers a process that automatically updates other fields, for example, External Status and / or Status.

If a Vault CRM instance uses the Account Territory Loader (ATL) to manage territories, approved DCRs also remove the territory from the territory\_\_v field of the appropriate account\_territory\_loader\_\_v record.

If territory assignments are managed via [Territory Assignment Rules](CreatingAssignmentRules.htm), removed accounts are re-added to territories when the rules next run.

To ensure DCRs are not accidentally sent to Veeva Network, DCRs created by this feature have a network\_customer\_master\_mode\_\_v field of 0. When using Decoupled DCRs with this feature, admins should verify any integrations with external systems to ensure DCRs created by this feature are not accidentally sent to external systems.

### Related Topics

[Using the Account Territory Loader](ATL.htm)

[Creating Territory Assignment Rules](CreatingAssignmentRules.htm)

[Creating and Assigning Territories](CreateTerr.htm)