> 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-p2p-fundraising-campaigns.md).

# Manage P2P Fundraising Campaigns

When a fundraiser creates a peer-to-peer fundraising campaign via FundraisingBox, the Connector automatically creates the related objects in Salesforce and links them accordingly.

Once the campaign exists in Salesforce, it can be edited and controlled in different ways:

### Edit a P2P Fundraising Campaign

{% hint style="info" %}
Only the data relevant for the Connector is synchronized back once it is changed 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 %}

#### Edit in Salesforce

Changes made directly within the Campaign fields in Salesforce are synchronized back to FundraisingBox for further processing.

{% hint style="warning" %}
The 'Thank you message', 'Campaign description', and 'Campaign image' are not synchronized from Salesforce. These must be updated via the FundraisingBox Edit Link provided within the campaign information.
{% endhint %}

#### Edit via FundraisingBox Edit Link

* The FundraisingBox Edit Link can be found within any Campaign the Connector created. When the Campaign is updated via Edit Link, the changes will be reflected in Salesforce and the FundraisingBox for further processing. 
* Usually, updates made by the P2P fundraising campaign initiator are also done via the FundraisingBox Edit Link, when provided to the fundraiser. 

### Control P2P Fundraising Campaign by Status

Within the standard process the Campaign object gets the status 'In Progress' once it is initially created. The status can be controlled from Salesforce via the Campaign Status field.

* Set P2P fundraising campaign as preferred by choosing the 'Preferred' Status
* Set P2P fundraising campaign as locked by choosing the 'Aborted' or 'Planned' Status
* Set P2P fundraising campaign as completed by choosing the 'Completed' Status
* Set P2P fundraising campaign as active by choosing the 'In Progress' Status

{% hint style="info" %}
If you want to check the content and information of the fundraising campaign before it is published, you can ask for the feature 'Manual Activation'. With that, the campaigns will be created in 'Planned' status and need approval by setting the status to 'In Progress' in order to be published. 
{% endhint %}

### Delete a P2P Fundraising Campaign

If a campaign created by the Connector is deleted in Salesforce, the Connector will also remove the corresponding fundraising campaign 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-p2p-fundraising-campaigns.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.