Manage project members

Get a token that can act as a user

Member writes are user-scoped. Use a 3-legged token, or a 2-legged token plus the User-Id header of a project or account admin. See Authentication.

Import the members

POST projects/:projectId/users:import adds up to 200 members in one request. Each entry needs an email and the products the member should get, where access is administrator, member or none.

{
  "users": [
    {
      "email": "member@example.com",
      "companyId": "9e2b1c...",
      "roleIds": ["1a2b3c..."],
      "products": [
        { "key": "projectAdministration", "access": "administrator" },
        { "key": "docs", "access": "member" }
      ]
    }
  ]
}

The response reports per-entry success and failure, so a partially valid batch still imports the valid rows — always inspect failures rather than relying on the status code alone.

Confirm the members landed

GET projects/:projectId/users lists members. Narrow it with filters and trim the payload with fields:

GET /construction/admin/v1/projects/:projectId/users?filter[status]=active&fields=name,email,status,accessLevels&sort=addedOn%20desc

Change access or role

PATCH projects/:projectId/users/:userId updates a single member — company, roles and per-product access. Send only the attributes you are changing.

Remove a member

DELETE projects/:projectId/users/:userId removes the member from the project. Hub membership is unaffected; use the hub admin operations for that.