> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/other/changes-from-ango-hub-legacy.md).

# Changes from Ango Hub Legacy

Here are the main changes between Ango Hub Legacy and the current version.

## New Features

### Workflow

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FpViYZylaMwHLCL1FIbTj%2Fimage.png?alt=media&amp;token=d69443fc-2157-43d4-a0a3-c343e385266f" alt=""><figcaption></figcaption></figure>

Workflows are an all-new way to set up your data labeling pipeline. In Legacy, you could only have an annotator label a task, then a reviewer review it. It all changes with Workflow, where you can set up projects as complex as having multiple labeling and review tasks, and involving logical stages, filtering, random selection, plugins, webhooks, and much more.

For example, you can set up a project such that each task is annotated by a labeler, then reviewed by two reviewers, and if a reviewer rejects a task, a webhook is sent to an URL of your choice. And that's just the tip of the iceberg. [See the page on Workflow for more](/core-concepts/workflow.md).

### 3D Medical Editor

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2F2SX09qKGeUH5Ai5JPDid%2Fimage.png?alt=media&amp;token=85b49d22-c941-4a66-8a69-9e09a23329cf" alt=""><figcaption></figcaption></figure>

Ango Hub now supports the annotating of NIFTI and NRRD files, with the `.nii`, `.nii.gz` and `.nrrd` extensions. By adding a *Medical Brush* tool to your project, you'll be able to annotate those files and to see your annotations in 3D. [Learn more here](/labeling/labeling-editor-interface/medical-labeling-editor.md).

### New Lead Role

A new role type was added: Lead. Leads are like managers in that they can access everything about the project, with the exception that they can't change the project's workflow and settings.

### Redefined Reviewer Role

Previously, reviewers were able to access everything in the project they were assigned to, with the exception of project settings. We felt this gave reviewers too much access.

That role is now called Lead, and reviewers can now only access the tasks they have specifically been assigned to, along with project instructions and issues they have opened or been mentioned in.

### Visual Refresh

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FDb0UAjO4ygKvEbE40OxO%2Fimage.png?alt=media&amp;token=e60ce8f6-033d-4812-9d7f-3f1465096b65" alt=""><figcaption></figcaption></figure>

Ango Hub's main labeling editor interface has been streamlined to maximize the space on what matters: the asset. We've reduced the footprint of our UI to provide more room for the asset, and moved the Submit button to the top so that it takes up less space.

## Deprecations

Benchmarks are no longer available.

Review filters, previously accessible from the Quality section of the Settings tab, are no longer available.

The "Review Status" and the "Consensus Distribution" dashboards are no longer available.

{% hint style="info" %}
Ango Hub has changed in a way that breaks compatibility with Legacy. As a result of this, data is now stored in a new database. You will not be able to access your existing Legacy account and projects in the new version, and Legacy projects cannot be ported as-is to the new version.
{% endhint %}

## Other Changes

* The project dashboard has been rewritten from scratch to be more performant and to show information that is relevant to each user as they log on.
* Integrations have been renamed system-wide to Storages.
* The Webhook section of the Organization page has been removed as webhooks can now be set up on a per-project basis through Workflow.
* Documentation is now located at a new domain: [docs.imerit.net](https://docs.imerit.net). Documentation for v2 is available at [docs.ango.ai](https://docs.ango.ai).
* Consensus is now available as [a stage within the Workflow functionality](/core-concepts/workflow.md#consensus).
* We've changed how pre-labeling works. To prevent accidental overwriting of annotations, we've limited pre-labeling to tasks in the *Start* stage. For more on pre-labeling in v3, see the page [*Importing Annotations*](/data/importing-and-exporting-annotations/importing-annotations.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.imerit.net/other/changes-from-ango-hub-legacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.