You have one Humanbased account. It stands for you as a person, and it can hold two roles: Developer and Contributor. Sign in at the Developer portal for organizationThe Developer-side unit that holds Campaigns, data access, and funds work, or at the Contributor portal for your own tasksA specific item a contributor claims or enters.
One person, one account, two roles
An account identifies a person, not a portal. Email, Google, GitHub, and Hugging Face are ways into that one account. A role describes what you do on the platform.
| Role | What you do | Where you work | How you get it |
|---|---|---|---|
| Developer | Commission data work, or use delivered data, on behalf of an Organization | Developer portal | Admission with an invitation code |
| Contributor | Claim tasks and submit your own work | Contributor portal | Sign up; no code is required |
You can hold one role or both. With both, you are still one person, and each role keeps its own records. CampaignsA developer's data-production project and its settings, data access, and billing belong to the Organization you act for. SubmissionsThe record created when work is submitted, ReputationA 0–100 score built from a Contributor's recorded work; it sets their tier and pay factor, and Earnings are yours personally.
To add a role or move between them, use the role control near your account menu at the bottom left:
- In the Developer portal, Platform role shows Contributor beside Developer. Select Contributor to switch. If it reads + Contributor, your account does not hold that role yet; selecting it opens a confirmation page before anything is created.
- In the Contributor portal, Switch to Developer Portal takes an account that holds both roles across without signing in again. Switch to Developer means your account is not a Developer yet; it opens Developer sign-up, which asks for an invitation code.
Keep to one account. A second account under another email address is not a second identity. It is a duplicate you will have to reconcile later, and changing your email onto an address that already holds the same role closes that account without keeping its data. Seeing the same email address in both portals does not by itself show that two accounts were joined; the role control shows which roles your account holds.
Sign in and recover access
The Contributor sign-in page offers email, Google, GitHub, and Hugging Face. New users choose Sign up.
If an existing Contributor password sign-in fails, check the email address, then use the emailed-code route or Forgot Password. A reset uses the code sent for that reset. After setting a new password, sign in with it if automatic sign-in does not finish.
If mail does not arrive, your account is under review, or the portal sends you to a role you did not expect, contact support with the portal, the time, and a redacted copy of the message. Creating another account does not repair the first one.
After signing in, open Account from the menu at the bottom left and check your personal details and linked sign-in methods. In the Developer portal, also confirm the active Organization before opening a Campaign, subscription, or bill. Your role in that Organization governs what you can do there; see Developer organizations.
Get Developer access with an invitation code
Developer accounts open by invitation. An invitation code admits your account to the Developer role; without one, sign-up stops before a Developer account is created.
Where you enter it. On Developer sign-up, in the field Invite or referral code. The same step applies when you sign up with Google, GitHub, or Hugging Face, and when you add the Developer role to an existing Contributor account.
Which codes work. A system invitation issued by Humanbased, or a Developer referral code.
What a code can be limited to. A number of uses, one portal, or one email address. Its issuer can also withdraw it. If yours is refused, check what you typed, then ask the issuer whether it is used up or was issued for a different address.
If you do not have one. On the sign-up page, next to Don't have one?, select Apply for developer access:
- Confirm your email address with the code sent to it.
- Answer a short survey.
- Wait for the decision by email. Humanbased may approve the application, ask for more information, or decline it.
An approval email carries your code. That code works once, and only for the address you applied with, so sign up with that same address.
After you are admitted. The code is not asked for again. Later sign-ins need only your usual sign-in method.
Three other invitations look similar and do different things:
| You were given | What it does | Does it open a Developer account? |
|---|---|---|
| A Campaign invitation code | Lets a Contributor join that one Campaign | No |
| An Organization invitation | Adds a Developer to that Organization | No. Get Developer access first, then accept it |
| A Contributor referral link | Records who referred a new Contributor | No |
When Contributors verify their identity
You can sign up as a Contributor without verifying your identity. Humanbased asks for it at two points:
- A Campaign requires it. The requirement is listed in Getting started on that Campaign, beside any course or agreement it needs.
- Your lifetime earnings reach a set level. Lifetime earnings count everything you have earned, including amounts you have not withdrawn. As you approach the level, the withdrawal checks in Earnings say that verification will be required. Once you reach it, withdrawals wait until verification passes. Your balance stays on the account, and nothing you have earned is lost.
Humanbased asks for two reasons:
- Compliance. Payouts are real money, and paying a person past a certain amount requires knowing who that person is.
- Data authenticity. Developers rely on the record of who produced their data. Verification ties a body of accepted work to one real person.
The level is not published and can change, so act on the notice in Earnings, not on a figure you heard elsewhere.
To verify, open Passport and select the Identity chip (or Verify now in Earnings), then read Before you submit before you provide a document or selfie. Qualifications, credentials, and Passport describes what happens to the material you submit. After verification passes, return to Earnings and reopen the checks; see Withdraw USDC and check its status.
Manage personal details and public visibility
Use Account for your personal name, photo, email, and sign-in bindings. Manage the Organization's name and billing contact under Organization instead.
In the Contributor portal, open Account → Public Profile to choose Public or Hidden for the entire page. If the page offers Claim your handle, complete that step and confirm the saved handle. Check the visibility setting and the actual profile address before sharing it.
Passport is your private record overview, separate from the public page. Bind Wallet associates a wallet with the account. Social binding is not currently available: the X card shows a locked Connect, and no Telegram card is offered.
Check messages and referrals
Use Inbox for Contributor messages, Learn for course results, and Earnings for reward records. In Inbox, choose Channel to switch between All messages and Conversations, and use Mark all read to clear unread notifications. It does not mark conversations: open each unread conversation to clear it. Most messages are notices, so there is no one to reply to. A conversation is how support asks you about something, and you can answer it with Send. There is no notification setting in the portal. Optional emails, such as announcements, carry their own unsubscribe link; sign-in and account emails do not, because they are not optional.
In Referral, copy a link from Your codes & links and open How it works before sharing it: it shows the current bonus rate and whether bonuses are paused. A person who registers through it creates a referral relationship; an accepted first contribution can activate it under the displayed terms. Check History → All / Pending / Valid for the relationship, then compare the referral reward with the actual entry in Earnings.
Registration, activation, reward processing, and money available to withdraw are separate events. If the underlying contribution reward is later canceled or adjusted, check the related referral reward again.
A referral does not join the person to an Organization, TeamA relationship among Contributors that leaves each member's Submissions and Earnings their own, or Campaign. The Developer Referral page has been removed; this does not mean historical Developer access codes are all invalid.
Close your account or request your data
Neither portal can close your account or export your data yourself today. The Developer portal shows Account → Delete account, but the request behind it is not implemented yet: confirming shows an error, and your sign-in, resources and any Contributor role stay as they were. The Contributor portal has no such option. To close an account or get your data from either portal, email hello@humanbased.ai from the address on the account. Withdraw any Contributor balance first. To have your identity-verification images deleted, say so in the same message.
Before changing your email
In Account → Change email, enter the new address, its verification code, and your current password. The old address stops working for sign-in after the change; it is not kept as a backup.
If the new address already has a Humanbased account, the result depends on its roles:
| Account at the new address | What happens |
|---|---|
| It has a portal role you do not yet have | That role joins your account as the same person, without a separate merge confirmation. |
| It has a role you already have | The account you are changing wins. The existing account at the new address is closed, and its data is not retained in the winning account. |
The change is blocked if an account to be closed still holds a balance or is the sole Owner of an Organization. Resolve the balance or transfer ownership through the appropriate account before trying again.
Changing email can close another account, and it is not a way to check whether one exists. Review both accounts and their data first. If you cannot establish the effect, contact support before submitting the change.