Sign in

v76

OpenAPI 3.0.3raw.githubusercontent.com2026-08-015764591.5 MB
Projects

✨ Get project members paginated

<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.

get/api/projects/{id}/members/paginated/

Path parameters

idinteger required

Query parameters

idsstring

Comma-separated list of user IDs to filter by

implicitboolean

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

last_activity__gtestring date-time

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

last_activity__ltestring date-time

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

no_annotatorsboolean

Exclude annotators from the results

orderingstring

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)

pageinteger

A page number within the paginated result set.

page_sizeinteger

Number of results to return per page.

rolestring

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.

searchstring

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

tagsstring

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

user_typestring[]

Multiple values may be separated by commas.

with_deletedboolean

Include deleted members in the results

Response

countinteger required
nextstring uri nullable
previousstring uri nullable

Example response

{
  "count": 123,
  "next": "http://api.example.org/accounts/?page=4",
  "previous": "http://api.example.org/accounts/?page=2"
}