Start with a data need

Sign in to the Developer portal. CampaignsA developer's data-production project and its settings, courses, data, and billing belong to an organizationThe Developer-side unit that holds Campaigns, data access, and funds; the same person can have different access in different organizations.

Before you begin

The Developer portal opens on its dashboard: Balance, Active Keys, and Subscriptions for the active organization, a Getting started checklist, and New Campaign.

1. If your teamA relationship among Contributors that leaves each member's Submissions and Earnings their own already uses Humanbased, ask its Owner or Admin for an invitation and join the existing organization. If you are starting independent work, create your own organization through the same guide. Do not create a second organization to work on a teammate's Campaign.
2. Check the active organization in the account menu and your role in Organization → Members. If the expected organization is missing, resolve access with its manager before editing resources.
3. Decide whether you need new human work or data already delivered. For example, to collect new labeled responses, follow Commission new work below. To retrieve an existing authorized subscription, begin with Get existing data.

Commission new work

Before opening Builder, prepare a short taskA specific item a contributor claims or enters description, the material a Contributor will submit, who may participate, how you will check quality, and an initial budget. Builder is the Campaign editor for turning those decisions into a draft and workflow. For example, a small labeling Campaign could ask eligible Contributors to label a limited set of records, require a review before acceptance, and deliver only accepted responses. This is an illustration, not a preset or a promise of delivery.

1. In Campaigns, choose Open Builder to create a draft. For an existing Campaign, open its card first, then enter Builder.
2. Define the work: describe the requested material, the Contributor's form, and the criteria for acceptance.
3. Configure the workflow: connect eligibility, human work, checks, acceptance, and delivery. Save the node and the canvas separately.
4. Test and launch: check pricing, budget, eligibility, and a dry run before selecting Launch. Check the Campaign's actual state afterward.
5. Once work begins, use Reviews for submissionsThe record created when work is submitted and review outcomes. Programmatic retrieval has separate delivery and subscription conditions.

Saving a draft does not publish it. A dry run does not create real tasks, earnings, or a production delivery.

To look at an earlier configuration, open History in Builder's bottom toolbar. An older version opens read-only, and restoring it creates a new latest version without overwriting any other. See Define work and participation requirements.

Take over existing work

The portal checks permissions for each action. If you need an API Key, any member of the active organization can create one; an Owner or Admin can revoke any key in the organization. API access and authentication covers the separate credential scope.