WhatsApp Business Account - Assigned Users Management API | Developer Documentation

Transfer responsibility without losing the working route

Use this checklist when the person who manages a ChatArchitect WhatsApp connection changes. Giving the successor access to one system does not establish access to every other part of the setup. A Meta assigned-users API is not a ChatArchitect customer-access endpoint.

List the responsibilities to hand over

Use the account-control check, business access and the settings ownership guide to establish which administrator can arrange each change. Do not assume an invitation to Meta grants a CRM login or changes the API credentials.

Verify the successor before withdrawing existing access

1. Agree on the needed tasks and arrange authorized access through each system's supported process.
2. Have the successor use their own permitted access to identify the intended account, number and connected tool.
3. For a custom service, confirm that the team can maintain the server-side credentials and receiver without copying Secret values into the handover note. Use the credential guide and receiver management.
4. Run an agreed incoming/outgoing test and check where the messages and results appear.
5. Arrange the authorized removal of obsolete access after the successor's tasks and recovery contact are confirmed.

If a former person knew API credentials, ask support and the integration owner to confirm the supported replacement/revocation procedure and its effect on sending and callbacks. Changing a Facebook password or removing an asset assignment does not by itself establish that a ChatArchitect credential pair was replaced.

Keep handover separate from a number move

If the change also involves another business, provider or number, use the change-planning checklist. This article does not promise account ownership transfer, credential rotation controls or a universal role model. Keep an accountable person for pending sends and incoming requests throughout the agreed change.