> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/service/list-the-users-a-service-order-can-be-assigned-to.md).

# List the users a service order can be assigned to

List the users of the tenant a service order at this store can be assigned to: exactly the users post-serviceorders-assign accepts as assignedUserUid at this store, so the picker and the assign never disagree. The store in the path is the store that owns the service order, as it is on the assign. Each item's tenantUserUid is the value assignedUserUid takes on post-serviceorders-assign. A user is listed when they can log in, are not an integration account, and hold SERVICE\_ORDER reaching this store — granted at the store, at its organization, or tenant-wide, the three adding up rather than the narrowest deciding, and a tenant-wide ADMIN grant counting as every permission; an ADMIN permission held at an organization or a store is not every permission there. The legacy tenant role grants nothing here, so a user with no role assignments is not listed. A deactivated user is left out; the tenant role is not read, so a blocked user is left out because blocking them through the user update deactivates them. A user whose e-mail invitation is not yet accepted is listed, because the assign accepts them. Who is asking changes nothing for a user of the tenant: a superadmin caller who is a user of the tenant gets the same list as anyone, and a superadmin is listed only on the grants they hold as a user of the tenant. A superadmin caller who is not a user of the tenant is refused with a 403. query narrows the list. It is matched case-insensitively and in part against the display name, the first name, the last name and the user code. E-mail and mobile are not matched, because the list never shows them. An empty or missing query lists everyone who can be assigned. The list is sorted by display name, with the tenantUserUid as the tiebreaker, and is paged, the paging counting the users who can be assigned; there is no sort parameter. Each item carries the user's uid and display name only — never the user's permissions, e-mail or mobile. A caller who does not hold SERVICE\_ORDER at the store in the path is refused with a 403, and a storeUid naming no store of the tenant with a 400.

Required permissions: SERVICE\_ORDER

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Service","description":"Service"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"responses":{"ServiceAssigneeListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/ServiceAssigneeResponseSchema"}},"paging":{"$ref":"#/components/schemas/Paging"}},"required":["items","paging"]}}}}},"schemas":{"ServiceAssigneeResponseSchema":{"title":"ServiceAssigneeResponseSchema","description":"A user a service order at the store can be assigned to, as the assignee list serves it. It carries the user's uid and display name only — never the user's permissions, e-mail or mobile.\ntenantUserUid is the value assignedUserUid takes on post-serviceorders-assign.","type":"object","required":["tenantUserUid","displayName"],"properties":{"tenantUserUid":{"$ref":"#/components/schemas/UID"},"displayName":{"type":"string","description":"The user's display name, the name the service order shows as assignedUserDisplayName once the user is assigned. It is served as stored, and it is empty for a user who has none, as assignedUserDisplayName is."}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"Paging":{"description":"totalCount The total number of items in the result set.\n\npageSize The number of items per page.\n\npageNumber The current page in the result set.","properties":{"pageNumber":{"type":"integer"},"pageSize":{"type":"integer"},"totalCount":{"type":"integer"}},"required":["totalCount","pageSize","pageNumber"],"title":"Paging","type":"object"}},"parameters":{"pageNumberQuery":{"description":"Reference to a specific page in a result set.","in":"query","name":"pageNumber","required":false,"schema":{"type":"integer"}},"pageSizeQuery":{"description":"The number of items per page in a result set.","in":"query","name":"pageSize","required":false,"schema":{"type":"integer"}},"serviceAssigneeQueryQuery":{"name":"query","in":"query","required":false,"schema":{"type":"string"},"description":"Narrows the list of users a service order can be assigned to. Matched case-insensitively and in part against the display name, the first name, the last name and the user code. E-mail and mobile are not matched, because the list never shows them. An empty or missing query lists everyone who can be assigned."}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/assignees":{"get":{"summary":"List the users a service order can be assigned to","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/ServiceAssigneeListResponse"}},"operationId":"get-serviceorders-assignees","description":"List the users of the tenant a service order at this store can be assigned to: exactly the users post-serviceorders-assign accepts as assignedUserUid at this store, so the picker and the assign never disagree. The store in the path is the store that owns the service order, as it is on the assign. Each item's tenantUserUid is the value assignedUserUid takes on post-serviceorders-assign.\nA user is listed when they can log in, are not an integration account, and hold SERVICE_ORDER reaching this store — granted at the store, at its organization, or tenant-wide, the three adding up rather than the narrowest deciding, and a tenant-wide ADMIN grant counting as every permission; an ADMIN permission held at an organization or a store is not every permission there. The legacy tenant role grants nothing here, so a user with no role assignments is not listed. A deactivated user is left out; the tenant role is not read, so a blocked user is left out because blocking them through the user update deactivates them. A user whose e-mail invitation is not yet accepted is listed, because the assign accepts them.\nWho is asking changes nothing for a user of the tenant: a superadmin caller who is a user of the tenant gets the same list as anyone, and a superadmin is listed only on the grants they hold as a user of the tenant. A superadmin caller who is not a user of the tenant is refused with a 403.\nquery narrows the list. It is matched case-insensitively and in part against the display name, the first name, the last name and the user code. E-mail and mobile are not matched, because the list never shows them. An empty or missing query lists everyone who can be assigned.\nThe list is sorted by display name, with the tenantUserUid as the tiebreaker, and is paged, the paging counting the users who can be assigned; there is no sort parameter. Each item carries the user's uid and display name only — never the user's permissions, e-mail or mobile.\nA caller who does not hold SERVICE_ORDER at the store in the path is refused with a 403, and a storeUid naming no store of the tenant with a 400.\n\nRequired permissions: SERVICE_ORDER","parameters":[{"$ref":"#/components/parameters/pageNumberQuery"},{"$ref":"#/components/parameters/pageSizeQuery"},{"$ref":"#/components/parameters/serviceAssigneeQueryQuery"}]}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/developers/api-documentation/service/list-the-users-a-service-order-can-be-assigned-to.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
