A CampaignA developer's data-production project and its settings brief, the form a Contributor completes, and the rules for joining are three separate parts of the setup. Configure each one before testing the Campaign.
Brief and work form
Open Setup → Campaign details. Give the Campaign a Campaign name and a short Brief so people can recognize it. Use the detailed/public description for the input material, action, submissionThe record created when work is submitted, and acceptance rule. Select Save changes before opening Builder. A draft shows the same fields again in the Settings step of Test & Launch, where a name, description, and cover are required before launch.
In Open builder, select the Supply / Human work node and choose the Task type. For source, label, evaluate, or synthesize work, select an existing Work UI → Form template, or use Create a new template if your organizationThe Developer-side unit that holds Campaigns, data access, and funds has none that fits. Add the required fields, bind the template to the step, and use Preview › to see what the Contributor will actually complete. Edit Template changes a selected template. Save the node, then save the canvas. No template selected means this step has no executable work interface; choose or create a compatible template before testing. An ordinary validate step instead selects the earlier human submission it reviews; it does not need a copy of that form.
For example, if the brief asks for one image and a category, the form needs a file field and a category choice whose options match the instructions. Preview a test answer and check that every required output has a place in the form. This example is illustrative; choose fields that fit the actual taskA specific item a contributor claims or enters.
Entry conditions
Use Entry Gate for applicable agreements, required courses, profile information, and Campaign invitation codes. For a course requirement, select the Program, version, and needed result. Finishing a course and mastering it are distinct conditions.
Qualification requirements filters self-reported profile information. An unset field imposes no requirement. Country or region matches the allowed residence list; education and experience use minimums; every listed skill and language level must match. A language entered twice uses its higher required level. This is not independent proof of identity or expertise. A certification mentioned only in the description is not an enforced gate; confirm an available credential and check before making it mandatory. Read course authoring for course preparation, workflow setup for Gate choices, and qualification guidance for verified credentials.
| Change you want | Edit here | Save scope |
|---|---|---|
| Brief and detailed instructions | Setup → Campaign details; in a draft also Test & Launch → Settings | This Campaign's details |
| Contributor form or work path | Open builder → Supply / Human work | Node Save, then canvas Save; in a running Campaign the canvas save publishes at once |
| Profile requirements | Draft Qualification requirements; running Setup → Requirements | Save requirements for this Campaign |
| Appearance and Contributor instructions | Draft Brand & theme; running Setup → Appearance | Save campaign theme affects this Campaign; Save as org default changes the organization's default |
| Pay and total budget | Human step reward; Test & Launch → Pricing & Budget | Check each step and the Campaign budget separately |
Save and revise
Use each area's Save changes or Save requirements control. Saving the workflow canvas does not save every brief or eligibility field. Return to the draft and check that the intended values remain.
In a draft, saving the canvas stores your work and changes nothing for Contributors. In a live or paused Campaign, saving the canvas publishes it. Builder first asks Apply these changes to a live campaign? and lists the nodes you added, removed, or changed, with the amount of work queued and in progress. Selecting Save and apply does three things at once:
- A new version is published immediately.
- Work that is queued moves to the new version.
- Work a Contributor has already started finishes on the version it began with. Finished work is not moved.
Select Keep editing to leave the running Campaign as it is. Builder refuses the save while work is still queued or in progress at a node you removed. A paused Campaign hands out no work, and the new version takes effect the moment it resumes.
After you confirm, Builder reports Now live and how many in-flight items moved to the new version. Nothing separates this save from Contributors receiving the new version: there is no test step in between.
View and restore canvas versions
Every successful canvas save creates a version. In Builder's bottom toolbar, select History to open Version history, which holds up to the 50 most recent saved versions. The list shows the latest 20 first; Show more loads the next 20.
Select a version to preview it. The canvas then shows that version's steps, connections, and layout read-only: you can pan and zoom, but you cannot edit a node, apply an Agent suggestion, or save. Back to current returns you to the version you were editing.
To bring an older canvas back, select Restore this version, then Restore as new version. The restore creates a new latest version from the old one; the version that was current and every earlier version stay in the history.
In a live or paused Campaign a restore also takes effect at once. The restored workflow applies to newly queued work and to pending work on steps it still contains. Work a Contributor has already started, and work waiting on a step the restored version no longer has, stay on the version where they began.
Two conditions stop these actions. If the canvas has unsaved changes, save or discard them before opening an older version. If someone else saved a newer version while you were previewing, reopen History and restore from the refreshed list.