Skip to main content

What workspace instructions do

Customize how Concord behaves across your entire organization by providing context about your business, goals, and preferences. Instructions help Concord understand:
  • Your business context and industry
  • Campaign management preferences
  • Key performance indicators and targets
  • Approval processes and constraints
  • Brand guidelines and messaging requirements

Setting workspace instructions

Open instructions

Edit workspace instructions in Concord.
1

Open settings

Click your profile in the top right and select “Settings”.
2

Go to Instructions tab

In the settings modal, click on the “Instructions” tab.
3

Add your instructions

Write instructions in the text area. Use ⌘↵ to save quickly.
4

Save changes

Click “Save” to apply instructions across all Concord interactions.

Instruction examples

Campaign structure:
Use Insertion Orders to segment by format (Display / Video), 
geography, and buying type. Do not mix budget logics within the same IO.
Naming conventions:
Campaign name = exact name of the brief.
IO names: country / format / objective / phase.
Apply detailed taxonomy only at Line Item level.
Splits & allocations:
Any split with a percentage allocation:
- If it impacts budget or structure → create separate IOs
- If tactical within the same structure → create separate Line Items
Budgets must be proportional to the defined allocation.
Governance:
- Never reallocate budget without explicit validation
- If information is missing → ask before proceeding
- Always talk to me in English

Best practices

Be specific: Define your naming conventions, split logic, budget rules, and approval thresholds explicitly. Include constraints: Mention brand safety requirements, blacklists, audience rules, and compliance needs. Cover missing info: Tell Concord what to do when information is absent — ask for clarification, use placeholders, apply defaults.
Workspace instructions are the single most impactful way to ensure Concord executes exactly how your team works. Treat it like an onboarding document for a new team member.