Who is allowed to say yes

If "the client" is four people, you will collect four opinions and zero permission. The founder likes the joke. The brand lead hates the crop. Legal has not opened the file. You need one name who can say this version may publish.

Other people can comment. They do not all get a veto unless the contract says they do. Write the name down on day one and put that person on the portal. When the name changes, change the access the same day.

A cheerful reply from last quarter's intern is not a sign-off. It is how you publish a discount the new manager did not authorize. Check the sender before you treat a message as final.

If two people both believe they are the approver, you do not have a backup. You have a conflict. Ask the client to pick in writing. Until they do, the post stays in internal review.

Send the frame, the caption, the date, and the network. Do not send a folder and a hope. The approver should be able to answer from a phone without opening your project tool.

If they need a colleague for legal or product claims, that colleague is a step, not a second owner. The named approver still closes the loop.

The scope should say who may approve, how many days they have, and what happens if they stay silent. Software can enforce a rule. It cannot invent one the sales call skipped.

When a new account manager inherits the client, the rule should be visible on the work, not trapped in your memory. That is the test. If they have to call you to learn who says yes, the process is still personal.