> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/resources/asset-sharing.md).
# Asset Sharing
To enable messaging on the WhatsApp Business Platform, assets within a Meta Business Portfolio must be shared with 360dialog. If a WhatsApp Business Account (WABA) is not shared with full control, messaging services will not function.
### Sharing a WABA
Sharing an asset allows 360dialog to access the WABA. This process can be done from within Meta Business Suite:
Meta Business Suite > Settings > Accounts > select WhatsApp Account > **Partners**
WABAs must be shared with 360dialog to enable messaging; without a full control assignment, messaging is not possible.
### Assign Partner Access
Follow these steps to check or assign Partner access to 360dialog.
{% stepper %}
{% step %}
Go to the **Meta Business Suite** and select the correct Business Portfolio.
Access it [here](https://business.facebook.com/latest/).
{% endstep %}
{% step %}
Go to **Business Settings**
{% endstep %}
{% step %}
Navigate to Accounts and select the specific WABA
{% endstep %}
{% step %}
Click Partners > **Assign Partner**
{% endstep %}
{% step %}
Enter the 360dialog Business Partner ID : `734443296905665`
{% endstep %}
{% step %}
Grant full control / Everything > **Assign**
{% endstep %}
{% endstepper %}
### BSP Permission Removed
If 360dialog full control is removed from a WABA, the following error message will be displayed in the 360Dialog Hub: `Please contact support. Something is preventing this number from working`
On the WABA, the status will be displayed: :red\_circle:**BSP PERMISSION REMOVED**
### WABA Sharing Methods
For messaging to resume, the Asset must be re-shared with 360dialog. There are two methods to do that.
1. [Re-Assign Partner Access](#assign-partner-access) using the above method.
2. Repeat the [Embedded Signup](/docs/hub/embedded-signup.md) and, during registration, select the existing WABA and complete the flow. The flow can be triggered using the Fix channel setup button as is described above.
### Asset sharing for Coexistence WABA
It is not possible to assign a partner to an existing WABA that contains a Coexistance number. Therefore, the registration process must be completed again as [described here](/docs/hub/embedded-signup/coexistence-onboarding.md). During Embedded Signup, make sure to select the same WABA in which the phone number was previously registered.
Below are the most common scenarios in which our BSP permissions are removed for coexistence numbers:
* The customer manually disconnects the number within the WhatsApp Business App.
* The customer logs out of the device running the WhatsApp Business App, including the device used during the initial onboarding.
* The number is banned within the WhatsApp Business App. Once the ban is lifted, the Embedded Signup process must be completed again.
---
# 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://docs.360dialog.com/docs/resources/asset-sharing.md?ask=&goal=
```
`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.