Project members
Project → Members (/projects/<id>/members, alongside Dashboard,
Data, and Settings in the project nav).
The roster of people who have access to this project, distinct from the organisation's member list. Two kinds of people appear here:
- Members — org members given an explicit project row, optionally with a project-specific role that overrides their org role.
- Contributors (public projects only) — people who joined through Discover without being in the org.
The page opens for Owner, Admin, Manager, the project creator, and platform staff. Editing (adding, changing roles, pausing, removing) is narrower: Owner, Admin, the project creator, and staff. A Manager opens the page read-only — no Add Members button, no role selectors, no row actions — and the server refuses the writes regardless of the UI.
How this differs from org membership​
| Organisation → Members | Project → Members | |
|---|---|---|
| Who is listed | Everyone in the org | Only people with an explicit project row (plus contributors on public projects) |
| Role | The org role — the default across every project | An optional per-project override; blank means inherit the org role |
| Adding | Invite links, email invites, existing users | Pick from existing org members only — the candidate list is the org's members not yet on the project |
| Removing | Leaves the org | Drops project access only; org membership is unaffected |
Owners and Admins always have access to every project in their org whether or not they appear in this list. Effective permissions on a project come from the project role when one is set, otherwise from the org role — see Roles + permissions.
Members tab​
Add Members​
Opens a picker of org members who are not yet on the project, with name/email search. Tick people and, per person, choose a role: Inherit org role (default), Owner, Admin, Manager, Reviewer, Annotator, or Guest. Only current org members can be added — a user who has left the org (or was never in it) is rejected. Each person added gets an in-app + email notification naming the project and their role.
The table​
Columns (toggle under View): Name, Email, Role, Role source, Quality (off by default), Actions. Search, a role filter, and a Hide inherited filter narrow the list; 10 per page by default.
- Role — a dropdown per row for editors. Changing it notifies the member of their new permissions. Setting it back to Inherit org role clears the override.
- Role source — Inherited (no override; changing the person's org role changes this project too) or Assigned (override set here).
- Quality — the member's last annotator-evaluation score, the number of ground-truth tasks it was computed on, and tasks used against the project's per-annotator limit. See Quality settings.
- Clicking a name opens the user's profile.
Pause, Resume, Re-enable​
All three flip the member's enabled flag; a disabled member sees
no tasks at all in this project until re-enabled (managers are
never filtered this way).
| Action | When it shows | Effect |
|---|---|---|
| Pause | Member is enabled | Disables access and sends the member an in-app notification; audited as project_member.pause. |
| Resume | Member was paused manually | Restores access and notifies them; audited as project_member.resume. |
| Re-enable | Member was auto-suspended by annotator evaluation (row shows a paused badge) | Restores access and clears the evaluation-suspend flag, so the next evaluation pass doesn't immediately re-suspend them on the old below-threshold score. |
The wording differs so a manager can tell a manual pause from an automatic suspension; both end in the same enabled state.
Remove​
Per row, or in bulk via the row checkboxes. Removes the project row only — the person's org membership is unaffected, and they're notified by in-app message and email. Someone who still holds an org role that grants access (Owner, Admin) keeps access through that role.
Contributors tab​
Appears only when the project is public (Visibility).
Lists ProjectContributor rows — people who joined from Discover —
split into pending requests and active contributors. No role column:
contributors have no project role.
- Pending requests (review-first projects) — Approve grants task access; Decline removes the request (they can request again later). If the requester has opted in to sharing their reputation profile, a one-line summary (validated units, acceptance rate, number of orgs) appears under their name and links to the full profile — see Reputation profiles.
- Make facilitator / Demote — appoints a contributor as a recruiter with an attributed invite link; demoting deactivates their link. See Facilitators.
- Remove — drops the contributor row. Their existing annotations stay attributed for audit and review; only access is revoked.
A manager who can open the page but not edit it (an org Manager) sees the roster without the Approve / Decline / Remove / facilitator buttons.
Gotchas​
- Adding someone here does not add them to the organisation; the picker only offers people who are already org members. Invite them via Organisation → Members first.
- A project-role override outranks the org role in both directions — an org Admin given the Annotator role on one project is an Annotator there.
- An evaluation auto-suspension shows as a paused badge and a Re-enable button, not Resume. Use Re-enable; otherwise the next evaluation pass re-suspends on the stale score.
- The member list and the contributor roster are manager-only on the server; annotators cannot enumerate either even if they reach the URL.
- Every add, role change, pause, resume, and removal is written to the org audit log.
What's next​
- Roles + permissions → — the role matrix behind inherited vs assigned roles
- Members + invites → — getting people into the organisation first
- Visibility → — turning on the Contributors tab by making a project public and open
- Auto-suspend rules → — org-level automatic pausing, as opposed to the per-project evaluation suspension shown here