Terminology Glossary
An authoritative dictionary of all 24 key terms, operational states, node definitions, and security concepts used throughout the Tensoract platform.
The process of labelling, tagging, or marking up data (text, images, audio, video) to train or evaluate AI models.
A task currently at the annotation step, available for an annotator to claim and work on.
A workflow node that routes tasks to human annotators for labelling work. Exactly one outgoing edge.
A user responsible for labelling tasks and submitting them for review.
A combined role allowing one user to both annotate and review tasks in the same project.
A role that grants access to generate API keys and invoke Tensoract APIs programmatically.
An administrator scoped to a single company with full operational access within that tenant.
A task approved by a reviewer. No further editing is possible.
A named collection of files of a specific type used to generate tasks in a project.
Full operational access to a specific dataset (upload, manage, export).
Read-only access to a specific dataset. Can view and download exports.
A task declined by an annotator or reviewer as unworkable. A decline reason is recorded.
The OIDC discovery endpoint of an identity provider, used to auto-configure SSO.
An additional security step requiring an OTP sent by email to verify identity on untrusted devices.
A standard authentication protocol. Tensoract supports any OIDC-compliant identity provider.
A 6-digit code sent to email to verify identity during login on an untrusted device.
A unique identifier on an outgoing edge of a PLUGIN node. External plugins use it to route tasks to the correct next step.
A task awaiting external automated processing. The PLUGIN workflow node routes tasks to external systems.
The main workspace combining datasets, workflows, taxonomies, and team members for annotation work.
Full operational access within a specific project.
Read-only access to a specific project. Can view dashboards and download exports.
A project configuration requiring multiple annotators to independently submit the same task before it advances.
A task returned to the Annotator by a Reviewer for corrections. A rejection comment is recorded.
Assesses annotator work. Can approve, reject, or decline tasks.
A QA workflow node with exactly two outgoing edges: approve and reject.
An annotator has submitted the task, awaiting a reviewer, and a task currently being reviewed.
A permission profile assigned to a user determining accessible sections and permitted actions.
Authentication via an external identity provider instead of Tensoract credentials.
A task generated but not yet opened; the entry point of every workflow.
Platform-level administrator with cross-tenant access. Manages companies, analytics, audit logs, and system settings.
A structured labelling schema defining what annotators can label (labels, hierarchies, relationships).
A ZIP-packaged HTML/Liquid annotation interface that defines what annotators see and interact with during a task.
Synonymous with Company. Each tenant is an isolated organisational unit with its own users and data.
A browser verified via MFA and authorised to skip the OTP step on future logins for a set period.
A configurable pipeline of connected nodes defining how tasks move through annotation, review, and completion.