> 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/workstation-orientation.md).

# workstation orientation

The Boom•Clap Workstation is the main control surface for Melody campaign owners.

Use it to create campaigns, review active campaigns, open campaign profile pages, manage status, and check reporting.

### What you can do

From the Workstation, campaign owners can:

* create Melody campaigns;
* review active campaigns;
* open campaign profile pages;
* check status, spend, reporting, and featured Spins;
* pause or resume campaigns when eligible;
* purchase Melody Credits when available;
* open the Melody and Resonance field guides.

<figure><img src="/files/a2hgpHgTAfgvQzO54ARN" alt=""><figcaption><p>Sample Workstation</p></figcaption></figure>

## Credits and access

The Workstation shows your current Melody Credit balance. One Melody Credit equals one US dollar of campaign budget.

A Melody campaign cannot be created with a budget larger than the available credit balance.

Creating Melody campaigns requires client level 2 or higher. Level 2 campaigns normally enter manual review. Eligible higher-level campaigns may be approved automatically under the current workflow.

### Campaign profiles

After a campaign is created, the Workstation opens the campaign profile. The profile is where you can review:

* campaign status;
* campaign budget and spending;
* current rates;
* valid impressions, clicks, and engagement sessions;
* featured Spins;
* pause and resume controls.

Next: [Submit a Campaign](/boom-clap-melody-field-guide/campaign-owners/submit-a-campaign.md)


---

# 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/workstation-orientation.md?ask=<question>&goal=<endgoal>
```

`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.