> 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/mapping-architecture/full-standard-mapping-table.md).

# Full Standard Mapping Table

The full mapping architecture of the FundraisingBox Nonprofit Cloud Managed Package is summarized in a standard mapping table. This table provides a detailed field-level representation of the architecture. 

Please access the table here: [Full Standard Mapping Table](https://docs.google.com/spreadsheets/d/1XiC6p_Fx2sJOX0JYWi2MmafMirlJOPWbsnIP5MrVUVk/edit?gid=795485192#gid=795485192)

{% hint style="info" %}
Every integration project is based on the standard mapping architecture. Within a customer project it serves as the central documentation of the target state and, upon project completion, as the documentation of the actual state.
{% 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/mapping-architecture/full-standard-mapping-table.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.