Context
Dualhook operates as a tech provider integration layer, not as a BSP (Business Solution Provider). Permission in this context means the customer has delegated the required Meta access so Dualhook can configure and operate integration features on their behalf.
What Permission Enables
With proper permission, Dualhook can:
- Configure webhook subscription and override
- Sync and manage templates
- Read health and account signals
- Perform phone-number-level operations needed for setup
Required Access Scope
The delegated access should include account, phone, template, and messaging tasks. In Dualhook-managed onboarding via Embedded Signup, required task scopes typically include:
| Scope | Purpose |
|---|---|
MANAGE | General WABA management |
DEVELOP | Development and testing access |
MANAGE_PHONE | Phone number configuration |
MANAGE_PHONE_ASSETS | Phone number asset operations |
MANAGE_TEMPLATES | Template CRUD operations |
MESSAGING | Send and receive messages |
Checking Permission
You can confirm permission in two places:
In Dualhook
- Connection is active
- Sync and health checks succeed
- Template operations are allowed
In Meta Business Settings
- The correct app or system user is assigned to the target WABA
- Required task scopes are present
Navigate to Meta Business Settings > Accounts > WhatsApp Accounts > select your WABA > Assigned People/Apps to verify.
If Permission Is Missing
Symptoms usually include:
- Subscription or override setup fails
- Template sync, create, or update fails
- Health checks return authorization errors (code
10or200— see API Error Reference)
Resolution
- Re-run the delegated onboarding/authorization flow (Embedded Signup).
- Ensure the correct Business Portfolio and WABA are selected.
- Confirm required task scopes are granted before retrying operations.
- If using a system user, verify it has the correct role and asset assignments.
For onboarding details, see Embedded Signup. For troubleshooting connection issues, see Troubleshooting.