Campaign notes that reach every week's brief, attached webpages and files with a real ready state, and overriding your workspace defaults for one campaign only.
Jump to module
The context notes field is what you typed when you created the campaign: "we are launching the new dashboard; lead with the time saved."
It is rendered verbatim into every weekly brief, under its own heading. Not trimmed, not reflowed, not summarised — your line breaks are yours.
That is what makes them worth writing carefully: on a four-week campaign, the sentence you type once steers all four weeks, not just the first.
What to put there:
What not to put there:
You can attach up to three sources to a campaign — a landing page, a menu, an event listing, a file — so the brief is written about the thing the campaign is actually for rather than about your business in general.
Each source carries a status, and the status is the load-bearing part:
Only ready sources reach generation. Nothing promotes a source to ready optimistically; an unknown or missing status is treated as pending, never upward. A source is never claimed as used before the system has actually read it. If a source shows failed, the campaign still generates — you picked an angle, and that was always enough on its own.
Webpages are fetched through an external extraction service rather than directly from Bolta's own network. That is a security property, not a vendor preference: a URL you paste could point at an internal address, and fetching it from our network would be a way to reach things nobody should reach. Fetching from elsewhere removes the class of problem instead of mitigating it.
Two bounds worth knowing: three sources per campaign, and roughly four thousand characters of text taken from each. A campaign is written about a thing, not researched from a reading list — and every character of source competes with your voice examples and your angle for room in the prompt.
The brand kit is not a source row. Whether your business profile is consulted is a setting (below), not an attachment. Having it in two places would give the gate two answers.
Campaigns can override your workspace and agent defaults for this campaign only. The keys available:
| Setting | What it controls |
|---|---|
| Business profile | Whether your brand facts are consulted at all |
| Sources scope | This campaign's sources only, or the whole brand kit |
| Media scope | This campaign's media only, or your full library |
| Image quality | Regular or pro |
| Library media | Which library media may be used, and how |
| Tone | The tone the writer works in |
| Post time | A default time of day, 24-hour |
| Timezone | The zone that time is in |
Every key is optional, and an absent key means "inherit". Choosing "Default" in the sheet deletes the key — it never writes a copy of the current default. This matters more than it sounds: a stored copy of a default is how the value you see and the value the runtime uses start disagreeing three months later when you change the workspace setting and one campaign silently keeps the old one.
Overrides are applied per key, campaign over job. Setting a tone does not reset the post time.
Practical uses:
Voice. A campaign can name the voice profile it writes in. Leaving it unset means "the workspace default", resolved when the run dispatches — which is what campaigns did implicitly before the field existed, now stated rather than assumed. The chosen voice is carried to every producer the week dispatches, so social posts, articles and emails from the same campaign all write in it.
This is what makes multi-brand agency work possible in one workspace: one campaign per brand, each naming its own voice, without swapping a workspace setting between them.
Workspace content defaults. You can save a default content plan at the workspace level, and every new campaign draft then starts from that plan instead of the angle's bare suggested mix. Two behaviours to know:
If a saved default filters down to nothing, it is treated as no default at all and the campaign falls through to the angle's suggested mix. A stale default degrades to the behaviour you had before you saved one.
The settings sheet is easier if you think in situations rather than keys.
Change as few keys as possible. Every key you set is a place where this campaign will stop tracking your workspace when you improve it later. Absent means inherit, and inherit is usually right.