Organisation overview
The Organization section in the sidebar is where org-level work happens — beyond a single project, but scoped to one org.
Visible to Managers and above (Owner / Admin / Manager, plus platform staff) — Annotators, Reviewers and Guests are sent back to their home page. Several tabs are Owner / Admin only. See Roles for who can do what.
The pages
| Page | Sidebar entry | Who | What it does |
|---|---|---|---|
| Overview | Organization → Overview | Manager+ | Dashboard summarising the org's state |
| Members | Organization → Members | Owner / Admin | Members + invites — see Members |
| Workspaces | Organization → Workspaces | Manager+ | Project grouping — see Workspaces |
| Analytics | Organization → Analytics | Manager+ | Cross-project analytics — see Analytics |
| Quality | Organization → Quality | Owner / Admin | Cross-project evaluations + quality by project — see Agreement |
| Review | Organization → Review | Owner / Admin | Cross-project review queue |
| Payouts | Organization → Payouts | Owner / Admin | Payout runs for paid annotation work |
| Policies | Organization → Policies | Owner / Admin | Org-wide governance policies — see Org policies |
| Activity | Organization → Activity | Owner / Admin | Audit-event feed scoped to this org |
| Health | Organization → Health | Owner / Admin | Whether the service is up and backed up, and usage against limits — see Health |
| Resources | Organization → Resources | Manager+ | Reusable org assets — Templates, Consent, Labels, Knowledge bases (see below) |
| Settings | Organization → Settings | Owner / Admin | Org identity, emails (the contact for annotators and members, the contact for the platform, whether owners get a copy), access defaults, auto-suspend, quotas, danger zone |
Resources
Organization → Resources collects the org's reusable asset libraries under one tab, with a strip of sections to switch between them:
| Sub-tab | What it holds |
|---|---|
| Templates | Project templates — reusable project blueprints |
| Consent | Consent template library — see Consent |
| Labels | Org-wide label library — see Labels Manager |
| Knowledge bases | Curated concept lists for typed feature layers — see Knowledge bases |
Visible to org Owner, Admin, and Manager.
Overview dashboard
The first page when you click into the org. Shows:
- Annotations (30 d): annotation volume over the last month
- Recent projects: the most recently updated projects with their counts
- Top contributors: annotators ranked by output
- Plan and usage (Owner / Admin only): one tile per capped resource (storage per project, members, projects, tasks) with used / limit and a bar; amber past 80 %, red at the limit; resources under review are marked. Request an increase sits in the header (hidden when nothing is capped) — see Quotas
- Members and Activity (Owner / Admin only): member roster summary and the latest audit events — full feed at Activity
Quick actions on the title row: New project (Manager+) and Invite (Owner / Admin). Useful as a quick "where is the org" view before diving into specific projects.
Activity feed
Organization → Activity is the org-scoped view of the audit log: membership changes, consent signatures and withdrawals, project lifecycle, settings and policy changes, and review-queue actions that touched records in this org. Each row names the action, who did it, what it targeted and when; a row expands to its recorded details. Filter by action type, actor and date. Owner / Admin only. Full detail: Activity feed.
For the platform-level audit log (cross-org), see Platform → Audit log.
Review (cross-project)
Organization → Review (Owner / Admin) is the cross-project review queue — a single landing page for overseeing review across multiple projects.
Aggregates the per-project review queues into one. Useful for:
- Lead reviewers who oversee multiple projects
- Reviewers who want to pick from the org's full backlog rather than enter one project at a time
- Bulk-assign workflows ("assign these tasks across these three projects to this reviewer")
Same filters as per-project review queues (by agreement, by model confidence, by annotator). Per-project review settings still apply — this page is just a UI aggregator.
Settings
Organization → Settings.
Org-level configuration. Visible to Owner and Admin (the Danger Zone tab is Owner-only):
- General: organisation avatar and details (name, description)
- Access: default role for new members, allowed email domains — see Members
- Auto-suspend: automatic member suspension rules — see Auto-suspend rules
- Hugging Face: one organisation token and who may import or push with it, by role and per member — see Hugging Face Hub
- Quotas: members, projects, tasks and storage per project with usage bars, read-only for the organisation (platform staff edit them), a Request an increase button and the history of past requests — see Quotas and requests
- Danger Zone: transfer ownership (see below), delete org
Quotas and requests
Every organisation is on a tier set by the platform team (see Org quotas): a cap on members, projects, tasks, and on the uploaded bytes each project may hold. Files in connected cloud storage are never copied and never count. Uploads that would not fit are refused before they are sent, with a message naming how much the project has left.
Requesting an increase (Owner / Admin): press Request an increase on the Overview strip or under Settings → Quotas. The form lists the capped resources with the current limit and what is in use; tick one or several, give the new limit for each, add a reason, send. Ask for everything at once or one thing at a time. A resource already under review is locked until the platform team answers; each item is answered on its own, and you are notified per decision (approved with the new limit, declined with the reason). Settings → Quotas keeps the history.
Transferring ownership
The Owner role can be reassigned to another active org member — Organization → Settings → Danger Zone → Transfer ownership (Owner or platform staff only):
- Pick a current org member
- Confirm — the previous Owner is automatically demoted to Admin
- The new Owner inherits all Owner-level permissions
Useful for handovers when the original Owner leaves the team or
needs to step back. The transfer is logged in the audit log
(action = org.transfer). Org-wide governance lives on the separate
Policies tab — see Org policies.
What's next
- Members → — managing who's in the org
- Workspaces → — grouping projects within the org
- Consent library → — managing org-wide consent
- Analytics → — analytics dashboards
- Roles → — permission matrix for each role