> For the complete documentation index, see [llms.txt](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/campaign-owners/review-and-approval.md). # review and approval Melody uses account-level approval rules to balance speed with creative and publisher quality. ## Level 2 campaigns Campaigns submitted by level 2 clients enter **In Review**. Boom•Clap checks the campaign destination, creative, contextual fit, and participation standards before activation. Review may consider: * whether the destination and media work; * whether the campaign cover is suitable for compact circulation; * whether campaign claims are clear and non-deceptive; * whether targeting and publisher preferences are coherent; * whether the campaign fits Boom•Clap community culture. ## Level 3 and higher campaigns Under the current workflow, level 3 and higher client campaigns can be approved automatically. Automatic approval does not remove the campaign owner's responsibility to follow participation standards. ## Editing after submission Campaign owners should treat submission as the final creative handoff. They can pause, resume, or drop an eligible campaign, but they cannot freely edit approved campaign content. This protects publishers from receiving materially different creative after approval. When a live campaign needs a destination, cover, description, image, geography, or placement-preference change, contact Boom•Clap support. Administrators can make controlled edits when appropriate. ## Participation standards Boom•Clap prioritizes campaigns that can contribute to contextual discovery without degrading surrounding content. Campaigns involving deceptive offers, low-quality dropshipping, crypto speculation, prediction markets, or other unsuitable categories are not eligible. Approval is contextual, not merely technical. A valid URL and image do not guarantee participation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://being-and-time.gitbook.io/boom-clap-melody-field-guide/campaign-owners/review-and-approval.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.