Annotation settings
Project → Settings → Annotation.
Instructions, prelabeling, per-task annotation rules, and skip behaviour. One Save button — settings apply the next time an annotator opens a task.
Visible to Owner, Admin, Manager. Annotators don't see the tab.
Labeling instructions​
Settings → Annotation → Labeling instructions holds the guidance annotators see. Write it in Markdown (headings, lists, bold, links, tables) or in HTML, or mix the two; it is rendered and sanitised the same way everywhere it appears: the Preview here, the Instructions modal in the editor, and the pop-up before labeling.
- Show before labeling opens the instructions automatically the first time an annotator enters the labeling stream; afterwards they are behind the info button in the editor's top bar.
- Add file uploads one image (PNG, JPG, GIF, WebP), PDF, video (MP4,
WebM) or audio file (MP3, WAV, OGG, M4A) to the project and inserts it
at the cursor: an image as
, a PDF as an embedded frame, video and audio as players. Files go into the project's own upload area and are served with the project-membership check, so only people who can open the project can open the file. The limit is 25 MB per file (operators can change it withINSTRUCTION_FILE_MAX_SIZE). - Preview opens the instructions in a modal rendered exactly as annotators will see them, using the text currently in the box, so you can check formatting before saving.
- Keep the operative rules near the top: annotators skim.
Images hosted elsewhere work too (), as long as the
link is reachable by every annotator. Embedded frames (<iframe>) work
for files on this site and for YouTube, Vimeo and Google Drive or Docs
players; use the site's embed address, for example
<iframe src="https://www.youtube.com/embed/VIDEO_ID" width="100%" height="360" allowfullscreen></iframe>.
Frames from any other site are blocked by the security policy. Operators
can change the list with LS_CSP_EMBED_HOSTS.
Prelabeling​
Seed new tasks with predictions so annotators only need to correct them, rather than labelling from scratch.
- Use predictions to prelabel tasks — when on, a model-version selector appears; pick which set of predictions to seed from. Predictions come from a connected ML backend or an imported predictions column.
- Prelabeled regions arrive editable — the annotator's submission is stored as their own annotation, with provenance kept separate from the prediction.
Annotations per task​
Enforce how many annotation regions an annotator must create on one task before they can submit:
| Mode | Effect |
|---|---|
| No minimum (default) | Submit is always allowed, even with zero regions |
| Exactly one | Submit blocked until exactly one region exists — single-answer QA, single-best label |
| One or more | Submit blocked until at least one region exists — ABSA and other multi-aspect tasks where "no aspects" is never a valid answer |
A region here is any entry in the submitted result — a bounding
box, a text span, a brush mask, and also a <Choices> or <TextArea>
answer. The server counts every result entry, so a single
classification answer satisfies Exactly one. Skips bypass the
rule; drafts are not checked until submit.
Skip behaviour​
What happens to a task when an annotator presses Skip:
| Option | Effect |
|---|---|
| Requeue for others (default) | The task goes back to the common queue, excluding the annotator who skipped it — a different annotator gets it |
| Requeue for me | The task returns to the end of the same annotator's own queue — they see it again later |
| Ignore skipped | The skip counts as a completed annotation — the task is finished and never comes back |
With Ignore skipped, skipped tasks still show as skipped in the Data Manager and exports; they just stop circulating in the labelling stream.
Submission requirements​
Whether an annotator can submit a task without labelling anything. Default: empty submissions are allowed (use Skip for tasks with genuinely nothing to label). Switch to Require at least one region or answer and the Submit button stays disabled until the annotator has labelled at least one region or answered at least one field — Skip remains available. Enforced in the editor and by the server.
Bulk mode​
Enable bulk mode adds a rapid-fire Bulk label view for annotators;
Bulk page size sets tasks per page (1–100, default 20). The toggle
is only available when the labeling config is a single <Choices>
control with no regions or free-text inputs — see
Bulk mode.
Looking for something else?​
Settings that used to be described here live on other tabs:
- Task sampling (Sequential / Random / Active learning) and annotator-facing language — Settings → General
- Maximum annotations per task, the per-annotator annotation limit, and annotator evaluation — see Quality settings
- Reviewer queues and accept/reject behaviour — Review settings
What's next​
- Review settings → — the reviewer-side configuration (queues, ordering, accept / reject behaviour)
- Task lifecycle → — how the
Quality tab's max-annotations threshold drives
COMPLETED - Audio QC → — server-side checks that run before an annotation submit is accepted