Teams with their current membership, for the assignment picker.
Also carries the team’s own scope: which asset categories, sites and work order types it is relevant to (category_ids/site_ids/work_order_type_ids — empty means unrestricted, not excluded), and which roles may see it at all (role_ids, same rule). category_ids is the equipment’s category, not the job’s own — a team is scoped to what it works on, not to why the job was raised. default_assignee_worker_id is who a work order is pre-filled to when this team is the one clear match for that scope, never applied automatically. lead_names is who work is coordinated through, from the members marked as leading it — a separate question, since the lead need not be the default assignee. A lead sees all of the crew’s work orders.
Organisation-wide rather than site-scoped, and site_ids does not change that: it says which sites a crew is offered for, which is coverage, where the site column it replaced was an access boundary deciding who could see the crew at all. Who may see it is still role_ids. site_ids replaced a location list that nothing could read — a job names a site always and a location only sometimes.
Headers
Limiting and Pagination
Limiting and Pagination
Preference
count=none Query Parameters
Filtering Columns
Ordering
Limiting and Pagination
Limiting and Pagination
Response
OK
60200Note:
This is a Foreign Key to assignable_workers.id.
Note: This is a Primary Key.
200
