✨ Get project members paginated
Changed onResponse 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.
Request
- Base URLhttp://localhost:8000
- URLhttp://localhost:8000/api/projects/{id}/members/paginated/
- AuthAPI key in header Authorization
Path parameters
Query parameters
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.
Add skills to each row: the member's skills with their status, those the filters payload matched first. Owners, Administrators and Managers only; ignored for other roles.
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
Exclude view-only users 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.
How the tags ids combine: any (at least one tag), all (every tag, the default), none (no selected tag).
Multiple values may be separated by commas.
Include deleted members in the results
Response
Example response
{
"count": 123,
"next": "http://api.example.org/accounts/?page=4",
"previous": "http://api.example.org/accounts/?page=2"
}Changes
- info
added the new optional
queryrequest parameterinclude_skills - info
added the optional property
//to the response with the status
- info
- info
added the new optional
queryrequest parametertags_operator
- info