> For the complete documentation index, see [llms.txt](https://solutions.fundraisingbox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/business-processes/manage-account-information.md).

# Manage Account Information

### **Account Data Changes**

Changes to account information (e.g., name or address) must be made directly in Salesforce. The connector automatically detects these updates and synchronizes them back to FundraisingBox to ensure data consistency.

{% hint style="info" %}
Changes only apply to accounts created by the FundraisingBox connector, and only the data relevant for the connector is synchronized back after being updated in Salesforce. The exact fields are listed in the [Standard Mapping table.](/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/mapping-architecture/full-standard-mapping-table.md)
{% endhint %}

### Existing donor makes a new donation with updated information

When a known donor makes a new donation through the FundraisingBox form using a new address, email address, or phone number, the account information is automatically updated in Salesforce.&#x20;

* Any new address, email, or phone number entered via the FundraisingBox form is stored as the primary address, email, or phone number.
* The previous address, email, or phone number is moved to the 'secondary' address, email, or phone number fields. For more details check the [Standard Mapping table.](/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/mapping-architecture/full-standard-mapping-table.md)

### Merge Accounts

If contacts are merged manually, the merge process must be carried out in Salesforce. The connector detects the merge and applies it accordingly, even if one of the merged contact objects was previously unknown to the connector.

To understand how automatic merging by the connector works, please refer to [Duplicate Management.](/knowledge-base/duplicate-management.md)

### **Delete an Account**

If an account created by the Connector is deleted in Salesforce, the Connector will also remove the corresponding contact in FundraisingBox.

{% hint style="danger" %}
Once deleted, it **cannot be restored**.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/business-processes/manage-account-information.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
