✨ Get project members paginated | API Reference

This endpoint is not available in Label Studio Community Edition. Learn more about Label Studio Enterprise

Retrieve the members for a specific project.

Response Fields:

implicit_member (boolean): Indicates if the user is an implicit member.
- true: User has access via workspace membership or organization role (Administrator/Owner)
- false: User is an explicit project member (added directly to the project)
project_role (string|null): Project-specific role override if assigned, null otherwise

Note: Users can have both explicit membership AND implicit access. The implicit_member field is false if the user has an explicit ProjectMember entry, regardless of whether they also have implicit access via workspace or org role.

<Card href="https://humansignal.com/goenterprise"> <img style="pointer-events: none; margin-left: 0px; margin-right: 0px;" src="https://docs.humansignal.com/images/badge.svg" alt="Label Studio Enterprise badge"/> <p style="margin-top: 10px; font-size: 14px;"> This endpoint is not available in Label Studio Community Edition. [Learn more about Label Studio Enterprise](https://humansignal.com/goenterprise) </p> </Card> Retrieve the members for a specific project. **Response Fields:** - `implicit_member` (boolean): Indicates if the user is an implicit member. - `true`: User has access via workspace membership or organization role (Administrator/Owner) - `false`: User is an explicit project member (added directly to the project) - `project_role` (string|null): Project-specific role override if assigned, null otherwise **Note:** Users can have both explicit membership AND implicit access. The `implicit_member` field is `false` if the user has an explicit ProjectMember entry, regardless of whether they also have implicit access via workspace or org role.

Authentication

AuthorizationToken

The token (or API key) must be passed as a request header. You can find your user token on the User Account page in Label Studio. Example: <br><pre><code class="language-bash">curl https://label-studio-host/api/projects -H "Authorization: Token [your-token]"</code></pre>

Path parameters

idintegerRequired

Query parameters

idsstringOptional

Comma-separated list of user IDs to filter by

implicitbooleanOptional

Include/Exclude implicit project members in the results. If not provided, explicit + implicit members are returned.

last_activity__gtedatetimeOptional

Filter by last activity time (ISO 8601 datetime). Returns users with last activity greater than or equal to this time.

last_activity__ltedatetimeOptional

Filter by last activity time (ISO 8601 datetime). Returns users with last activity less than or equal to this time.

no_annotatorsbooleanOptional

Exclude annotators from the results

orderingstringOptional

Ordering field. Prefix with "-" for descending order. Allowed fields: id, email, first_name, last_name, username, last_activity, role, date_joined **Note on role ordering:** When ordering by "role", the system uses the effective role: - Project-specific role if assigned (takes precedence) - Organization role if no project role is assigned Roles are sorted alphabetically by their code: AD (Administrator), AN (Annotator), DI (Disabled), MA (Manager), NO (Not Activated), OW (Owner), RE (Reviewer)

pageintegerOptional

A page number within the paginated result set.

page_sizeintegerOptional

Number of results to return per page.

rolestringOptional

Filter members by role. Accepts single role or comma-separated list of roles. **Format:** - Single role: `?role=RE` - Multiple roles: `?role=AN,RE` (users with ANY of these roles) **Role Codes:** - `OW` = Owner - `AD` = Administrator - `MA` = Manager - `RE` = Reviewer - `AN` = Annotator **Matching Logic:** Returns users who have any of the specified roles either: 1. As their **project-specific role** (from project role assignments), OR 2. As their **organization role** (if they have no project-specific role override) **Note:** Project-specific roles take precedence. If a user has a project role assigned, their organization role is ignored for filtering purposes.

searchstringOptional

Search term for filtering members by name, email, or username

tagsstringOptional

Filter members by tags. Use a comma-separated list of tag IDs.

with_deletedbooleanOptional

Include deleted members in the results

Response

countinteger

resultslist of objects

nextstring or nullformat: "uri"

previousstring or nullformat: "uri"

This endpoint is not available in Label Studio Community Edition. Learn more about Label Studio Enterprise

Retrieve the members for a specific project.

Response Fields:

implicit_member (boolean): Indicates if the user is an implicit member.
- true: User has access via workspace membership or organization role (Administrator/Owner)
- false: User is an explicit project member (added directly to the project)
project_role (string|null): Project-specific role override if assigned, null otherwise

The token (or API key) must be passed as a request header. You can find your user token on the User Account page in Label Studio. Example:

curl https://label-studio-host/api/projects -H “Authorization: Token [your-token]”

Comma-separated list of user IDs to filter by

Include/Exclude implicit project members in the results. If not provided, explicit + implicit members are returned.

Filter by last activity time (ISO 8601 datetime). Returns users with last activity greater than or equal to this time.

Filter by last activity time (ISO 8601 datetime). Returns users with last activity less than or equal to this time.

Exclude annotators from the results

Ordering field. Prefix with ”-” for descending order. Allowed fields: id, email, first_name, last_name, username, last_activity, role, date_joined

Note on role ordering: When ordering by “role”, the system uses the effective role:

Project-specific role if assigned (takes precedence)
Organization role if no project role is assigned

Roles are sorted alphabetically by their code: AD (Administrator), AN (Annotator), DI (Disabled), MA (Manager), NO (Not Activated), OW (Owner), RE (Reviewer)

A page number within the paginated result set.

Number of results to return per page.

Filter members by role. Accepts single role or comma-separated list of roles.

Format:

Single role: ?role=RE
Multiple roles: ?role=AN,RE (users with ANY of these roles)

Role Codes:

OW = Owner
AD = Administrator
MA = Manager
RE = Reviewer
AN = Annotator

Matching Logic: Returns users who have any of the specified roles either:

As their project-specific role (from project role assignments), OR
As their organization role (if they have no project-specific role override)

Note: Project-specific roles take precedence. If a user has a project role assigned, their organization role is ignored for filtering purposes.

Search term for filtering members by name, email, or username

Filter members by tags. Use a comma-separated list of tag IDs.

Include deleted members in the results

The token (or API key) must be passed as a request header. You can find your user token on the User Account page in Label Studio. Example:

curl https://label-studio-host/api/projects -H “Authorization: Token [your-token]”

Ordering field. Prefix with ”-” for descending order. Allowed fields: id, email, first_name, last_name, username, last_activity, role, date_joined

Note on role ordering: When ordering by “role”, the system uses the effective role:

Project-specific role if assigned (takes precedence)
Organization role if no project role is assigned

Roles are sorted alphabetically by their code: AD (Administrator), AN (Annotator), DI (Disabled), MA (Manager), NO (Not Activated), OW (Owner), RE (Reviewer)

Filter members by role. Accepts single role or comma-separated list of roles.

Format:

Single role: ?role=RE
Multiple roles: ?role=AN,RE (users with ANY of these roles)

Role Codes:

OW = Owner
AD = Administrator
MA = Manager
RE = Reviewer
AN = Annotator

Matching Logic: Returns users who have any of the specified roles either:

As their project-specific role (from project role assignments), OR
As their organization role (if they have no project-specific role override)

Note: Project-specific roles take precedence. If a user has a project role assigned, their organization role is ignored for filtering purposes.

1	{
2	"count": 123,
3	"results": [
4	{
5	"active_organization_meta": "Acme Corp",
6	"avatar": "https://example.com/avatars/jdoe.png",
7	"id": 101,
8	"implicit_member": false,
9	"initials": "JD",
10	"last_activity": "2024-04-10T16:45:00Z",
11	"lse_fields": {
12	"email_notification_settings": "daily_summary",
13	"invite_expired": "false",
14	"invite_expired_at": "2024-12-31T23:59:59Z",
15	"invite_activated": true,
16	"invited_at": "2023-11-15T10:00:00Z",
17	"invited_by": 12,
18	"onboarding_state": "complete",
19	"social_auth_finished": true,
20	"trial_company": "Acme Corp",
21	"trial_experience_labeling": "Experienced with image annotation",
22	"trial_license_enterprise": true,
23	"trial_models_in_production": "Object detection, NLP",
24	"trial_role": "annotator_team_manager"
25	},
26	"organization_membership": {
27	"active": "active",
28	"organization_id": 42,
29	"role": "MA"
30	},
31	"pause": "none",
32	"project_role": "RE",
33	"tags": [
34	{
35	"id": 7,
36	"label": "QA Team"
37	}
38	],
39	"user_type": "human",
40	"username": "jdoe",
41	"org_membership": [
42	{
43	"active": "active",
44	"organization_id": 42,
45	"role": "MA"
46	}
47	],
48	"active_organization": 42,
49	"allow_newsletters": true,
50	"custom_hotkeys": null,
51	"date_joined": "2023-11-20T14:22:00Z",
52	"email": "jane.doe@example.com",
53	"first_name": "Jane",
54	"last_name": "Doe",
55	"phone": "+1-555-123-4567"
56	}
57	],
58	"next": "http://api.example.org/accounts/?page=4",
59	"previous": "http://api.example.org/accounts/?page=2"
60	}

$	curl http://localhost:8000/api/projects/1/members/paginated/ \
>	-H "Authorization: Token <api_key>" \
>	-H "Content-Type: application/json"