Managing Zalo OA for Multiple Brands: Permissions, Profiles and IPs
Updated:
Managing Zalo Official Accounts for several brands works best when three things are right: each OA belongs to the business that owns the brand, staff or agencies are added with only the permissions they need, and every admin signs in from a fixed environment with a stable Vietnamese IP. A proxy does not replace permissions; it keeps each login session consistent and keeps clients separate. This guide is for agencies, marketing teams and sellers who look after many OAs at once.
How an OA differs from a personal Zalo account
A Zalo Official Account is the official presence of a business, shop or organisation on Zalo. Users follow it to receive updates, chat with the shop and browse products. Unlike a personal account, an OA has no password of its own; you manage it through personal Zalo accounts that have been granted admin rights, in the OA management page or app.
Two things follow. First, the OA is only as secure as each personal account that can administer it. Second, when many people manage many OAs, the key question is who signs in from where and on which device, not how many passwords the OA has.
OA plans, features and verification steps are set by Zalo and change over time, so check Zalo's official pages before planning for a client.
Ownership and permission rules
- The business keeps ownership: create and verify the OA with the brand owner's own details. An agency should not register a client's OA in its own name; handing it over later is painful.
- Least privilege: Zalo lets you add managers with different permission levels. Chat agents only need to answer messages, content staff need posting rights, and full control stays with the owner plus one backup.
- Real personal accounts: every admin uses their own Zalo account with their own phone number and turns on the account protection Zalo offers. Never share one account between several people.
- Remove access when people leave: keep a list of who has access to which OA and review it monthly. It is simple and the most often forgotten step.
What the IP does in OA management
If one personal account administers five OAs for five clients, every admin action comes from that account. The IP does not separate the clients' OAs from each other; permissions do. So where does a proxy help?
Consistency. Agency staff work from home, cafes, the office and abroad. Every network change is a login from a different place and can trigger verification. A fixed Vietnamese IP per admin makes the work session look the same every day.
Client separation at the session level. If the agency uses a separate admin account for each client, give each account its own browser profile and IP so cookies, sessions and browsing history never mix.
Working from abroad. Staff outside Vietnam can route their admin profile through a Vietnamese proxy instead of hopping between countries.
Setup patterns for agencies
The last row matters: API integrations run from a server and use that server's IP. Proxies are for human login sessions.
| Situation | Arrangement | Suggested IP |
|---|---|---|
| One staff member manages many OAs with one account | One fixed browser profile and one fixed IP | Static ISP, Vietnam |
| Each client has its own admin account | One antidetect profile and one IP per account | Private IPv4 or ISP, Vietnam |
| Chat team working in shifts | One account and one machine or profile per agent | Private IPv4, Vietnam |
| Staff working abroad | Fixed profile routed through a Vietnamese IP | Static ISP, Vietnam |
| Messages sent via API from a server | Call the API from the business's own server | No proxy needed |
Setting up an admin profile
- Buy a suitable Vietnamese IP: a static Vietnam ISP proxy for lead admins, private Vietnam IPv4 for larger chat teams.
- Create a profile in your antidetect browser, add the proxy as
ip:port:user:pass, set the Asia/Ho_Chi_Minh time zone and Vietnamese language. See the AdsPower and GenLogin guides. - Open the IP checker inside the profile to confirm the proxy IP, then run the WebRTC leak test.
- Sign in to the admin account with a QR code from its owner's phone and open the OA management page.
- Record in an internal sheet which profile, IP and account has rights on which OA, so you know exactly what to revoke when someone leaves.
What a proxy cannot do
A proxy does not raise an OA's messaging limits, does not let you message people who have not followed the OA, and does not shield the OA from action under Zalo's content policies. If an OA floods followers with promotions and gets blocked and reported, a new IP will not save it.
A proxy is also not a VPN and adds no encryption; your connection to Zalo is protected by HTTPS as usual. See proxy vs VPN for the difference. Many brands also run staff sales accounts next to the OA; those follow the rules in managing multiple Zalo accounts, and wider client work is covered in social media management.
Frequently asked questions
Do I need a proxy to manage a Zalo OA?
No. A proxy helps when admins work from many places, or when an agency wants each client's sessions separated on a fixed Vietnamese IP.
Should an agency register the OA on behalf of a client?
No. The OA should belong to the brand owner; the agency gets management rights that are removed when the contract ends.
If one account manages several OAs, can problems spread between them?
Every action is tied to that account, so if it is restricted, managing all those OAs is affected. Keep at least one backup admin per OA.
ISP or IPv4 proxy for OA admins?
Lead admins are better on static Vietnam ISP IPs. Larger chat teams can use private Vietnam IPv4 to save money.
Does sending OA messages through the API need a proxy?
No. API integrations run from your server with its own IP. Proxies are for human admin sessions.
Fixed Vietnam IPs for your OA team
One dedicated IP per admin, unchanged for the whole rental, renewable from the dashboard so it never switches mid-project.
See Vietnam proxy pricing