> 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/core-concepts/user-roles.md). # User Roles Overview of user roles and permission levels in Ango Hub

All users in Ango Hub belong to both organizations and projects. As such, all users have different roles both at the organization and the project level. This page is an overview of all roles available to users, both at the organization and at the project level. {% hint style="info" %} For more on inviting new users to your organization, and on organization-level roles in detail, check the [Organizations](/core-concepts/organizations.md#inviting-new-users-to-your-organization-admin-only) page. For more on inviting users to projects, and on project-level roles in detail, check the [Managing Users in Projects](/labeling/managing-users-in-projects.md) page. {% endhint %} ## Organization-level user roles

Level	Role	Properties
Organization	Owner	Can see and edit all data in all projects in organization (equivalent to having the Manager role in all projects) Can invite and remove org members Can edit other members' org- and project-level role Can see org-level statistics Can see Ango Hub usage/plan details Can install and remove plugins Can create API key Can delete the organization Currently, there can only be one owner in an organization. Ownership transfer is not yet available from the user interface.
Organization	Admin	Everything the owner can do, except deleting the organization.
Organization	Member	Cannot see/edit organization-level data (statistics, plugins, usage, etc.) Can only see assigned projects In projects, can only see data according to assigned project-level role

Level

Role

Properties

Organization

Owner

Can see and edit all data in all projects in organization (equivalent to having the Manager role in all projects)
Can invite and remove org members
Can edit other members' org- and project-level role
Can see org-level statistics
Can see Ango Hub usage/plan details
Can install and remove plugins
Can create API key
Can delete the organization

Currently, there can only be one owner in an organization. Ownership transfer is not yet available from the user interface.

Organization

Admin

Everything the owner can do, except deleting the organization.

Organization

Member

Cannot see/edit organization-level data (statistics, plugins, usage, etc.)
Can only see assigned projects
In projects, can only see data according to assigned project-level role

## Project-level user roles

Level	Role	Properties
Project	Labeler	Available actions: Labeling Opening, responding to, solving, deleting own issues Available data Assets he has labeled Tasks he has completed Project instructions and samples Personal statistics Issues in which he's been mentioned or he's opened
Project	Reviewer	Everything a Labeler can do/see, plus: Available actions: Reviewing
Project	Lead	Everything a Reviewer can do/see, plus: Available actions: Adding, re-queuing, reassigning, deleting labeling tasks Set samples Opening, responding to, solving, deleting any issue Set benchmark tasks Add, edit, and remove project members See the Workflow tab (but not edit it) Bulk accept/reject tasks in Review stages Bulk requeue tasks from workflow stage settings Available data Tasks assigned to them and project settings.
Project	Manager	Everything a Lead can do/see, plus: Available actions: Exporting labels Editing all project settings

## User Permission Rubric ### **Organization**

Task	Admin	Member
See assigned projects and act in their according to their project role	✅	✅
See and edit all data in all projects	✅	❌
Invite organization members	✅	❌
Remove organization members	✅	❌
Edit other members’ organization-level roles	✅	❌
Edit other members’ project-level roles	✅	❌
See organization-level statistics	✅	❌
See Ango Hub usage/plan details	✅	❌
Install plugins	✅	❌
Remove plugins	✅	❌
Create API key	✅	❌
Access unassigned projects	✅	❌

### **Project**

Task	Labeler	Reviewer	Lead	Manager
Labeling assets	✅	✅	✅	✅
Viewing assets they labeled	✅	✅	✅	✅
Viewing tasks they completed	✅	✅	✅	✅
Viewing project instructions	✅	✅	✅	✅
Viewing personal statistics	✅	✅	✅	✅
Viewing issues they are mentioned in or opened	✅	✅	✅	✅
Viewing tasks assigned to them	✅	✅	✅	✅
Opening, responding to, solving, deleting own issues	✅	✅	✅	✅
Reviewing labels	❌	✅	✅	✅
Opening all issues	❌	✅	✅	✅
Responding to, solving, deleting all issues	❌	✅	✅	✅
Setting benchmark tasks	❌	❌	✅	✅
Requeuing tasks	❌	❌	✅	✅
Adding/editing/removing project members	❌	❌	✅	✅
Exporting labels	❌	❌	✅	✅
Viewing project-wide statistics	❌	❌	✅	✅
Run export plugins	❌	❌	✅	✅
Set tasks as benchmarks	❌	❌	✅	✅
Assign tasks to users	❌	❌	✅	✅
Assign tasks to batches	❌	❌	✅	✅
Adding and deleting assets	❌	❌	❌	✅
Viewing settings of the project	❌	❌	❌	✅
Editing settings of project	❌	❌	❌	✅

--- # 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/core-concepts/user-roles.md?ask=&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.