Access to an account does not mean every person should decide on the same things.
Resolve disagreements that currently happen in chat
An agency prepares a campaign for a logistics business. The commercial lead wants to broaden an offer, marketing reviews the message and the media specialist needs to know whether the budget can change. Everyone participates, but they are not approving the same thing. Treating those conversations as general permission to publish loses the distinction between authorizing a creative, accepting investment and validating a commercial condition.
List recurring decisions and name their owners. Every adjustment does not need a long chain. It does need a distinction between what the operating team can resolve and what requires client review. Agree on that before a deadline makes the campaign urgent.
Separate the request from authorization
Someone identifying a need can prepare a proposal without permission to apply it. Describe the reason, account, campaign, change and what should remain unchanged. The client’s response can then be understood as approval of that proposal or a request for an alternative.
Define what happens when the responsible person is unavailable. Absence should not become approval by habit. Also agree on returning incomplete requests: what information is missing and who supplies it. Rejection without explanation only sends the same work around again.
Give proposals a visible review process in Ads
Wiwo.Ads gathers team requests and their approval process. Responsible people can review proposals and decisions; actions on connected platforms depend on configured permissions and scope. The tool helps when that configuration reflects the actual agency-client agreement.
Review with participants which accounts belong to each client and which changes can be applied. Do not infer permissions from job titles. Before activating an operation, test the process with a representative request and check what each person needs to review, including creative material when it forms part of the change.
Keep a reference when teams change
A shared operation does not end at publication. Preserve reasons for decisions and review access when someone changes roles. Wiwo.Ads audit history lets teams consult recorded requests, decisions and changes, using available filters to review participation and periods.
Use the record in follow-up meetings to clarify facts, not replace discussion. If decisions appear that nobody recognizes as their own, the responsibility agreement may be incomplete. Correct that and test the process again before adding more people or accounts to the operation.
Frequently asked questions
Does creative approval also authorize the budget?
Do not assume so. Messaging, investment and configuration may have different owners; agree on what each authorization covers.
Does Ads apply every change requested by a client?
Actions depend on configured connections, permissions and approvals. Requests need the process and scope agreed for that operation.
