> 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-tenants-stores-for-the-service-screens.md).

# List the tenant's stores for the service screens

List every store of the tenant, inactive stores included and marked by isActive, so the service screens can name a store the caller holds no permission at: the destination picker of post-serviceorders-move, which needs no permission at the destination, the storeUids filter of serviceorders-search-tenant, and the store that owns a service order found there. It is granted to a user holding SERVICE\_ORDER or SERVICE\_STORE\_CONFIG at the tenant, at an organization or at any one store, or SERVICE\_CONFIG, which is held at the tenant only. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them, a user with no role assignments included, is refused with a 403. Each item carries the store's uid, its name, its organization and whether it is active, and nothing else of the store. The list names stores and never says where the caller may work: that is read from the caller's own permissions, and get-tenants-stores stays the list of the stores the caller holds any permission at. The list is not paged: the tenant's list of stores bounds it. It is ordered by store name, with the storeUid as the tiebreaker.

Required permissions: SERVICE\_ORDER, SERVICE\_STORE\_CONFIG, SERVICE\_CONFIG

```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":{"ServiceStoreListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/ServiceStoreResponseSchema"}}},"required":["items"]}}}}},"schemas":{"ServiceStoreResponseSchema":{"title":"ServiceStoreResponseSchema","description":"One store of the tenant as the service screens name it: its uid, its name, the organization it belongs to and whether it is active, and nothing else of the store. It names a store and never says whether the caller may work there.","type":"object","required":["storeUid","name","organizationUid","isActive"],"properties":{"storeUid":{"$ref":"#/components/schemas/UID"},"name":{"type":"string"},"organizationUid":{"$ref":"#/components/schemas/UID"},"isActive":{"type":"boolean"}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"}}},"paths":{"/tenants/{tenantUid}/serviceorders/stores":{"get":{"summary":"List the tenant's stores for the service screens","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/ServiceStoreListResponse"}},"operationId":"get-serviceorders-stores","description":"List every store of the tenant, inactive stores included and marked by isActive, so the service screens can name a store the caller holds no permission at: the destination picker of post-serviceorders-move, which needs no permission at the destination, the storeUids filter of serviceorders-search-tenant, and the store that owns a service order found there.\nIt is granted to a user holding SERVICE_ORDER or SERVICE_STORE_CONFIG at the tenant, at an organization or at any one store, or SERVICE_CONFIG, which is held at the tenant only. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them, a user with no role assignments included, is refused with a 403.\nEach item carries the store's uid, its name, its organization and whether it is active, and nothing else of the store. The list names stores and never says where the caller may work: that is read from the caller's own permissions, and get-tenants-stores stays the list of the stores the caller holds any permission at.\nThe list is not paged: the tenant's list of stores bounds it. It is ordered by store name, with the storeUid as the tiebreaker.\n\nRequired permissions: SERVICE_ORDER, SERVICE_STORE_CONFIG, SERVICE_CONFIG"}}}}
```


---

# 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-tenants-stores-for-the-service-screens.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.
