# BAU Designing **BAU (Business-as-Usual) assets** in Desire follows the same workflow as campaign-based asset creation. The only difference occurs at the very first step of the creation wizard, where the operator selects **BAU** instead of **Campaign**. Once this selection is made, the subsequent steps—asset setup, editing, approvals, and exporting—remain identical to the campaign flow, ensuring a consistent user experience. BAU assets are managed through a dedicated **BAU Dashboard**, which provides its own listing and search capabilities tailored for always-on or recurring assets. This separation helps teams clearly distinguish BAU work from time-bound campaigns, while still benefiting from the same powerful creation, governance, and export mechanisms used across the platform. We recommend that you review the [campaign-related documents](https://docs.desire.acik.in/basics/campaigns) if you haven't already and everything in BAU follows the same approach. --- # Agent Instructions: 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: ``` GET https://docs.desire.acik.in/basics/bau.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.