---
search:
  tags:
    - Layouts
    - GET
seo:
  description: >-
    List who a layout is shared with: its grants, and whether it is… Reference
    for the GET /v1/layouts/id/{layout_id}/access endpoint in the Roboto REST
    API.
sidebar:
  label: Get layout access
  badge: GET
title: Get layout access
type: openapi-operation
---
List who a layout is shared with: its grants, and whether it is restricted. A restricted layout is personal: only
its creator, the people and groups it is shared with, the org's admins and Roboto staff open it.

Requires permission to open the layout. A layout that does not exist, or is not in the caller's org, answers 404; a
caller who may not open it gets 401.

#### Access control
 - Restricted tokens need the API scope `api.everything_else`

`GET /v1/layouts/id/{layout_id}/access`

**Responses**

- `200` — OK
- `400` — A conversation with Roboto's AI is longer than the AI model can read at once. The conversation's messages and tool results, together with the AI's instructions, exceed the model's context window. The exception does not carry the token count or the model's limit.
- `401` — The caller's token is expired or malformed.
- `403` — The request would take the user or organization past a limit on a resource, such as AI credits.
- `404` — The request names an API route Roboto does not serve.
- `409` — The request conflicts with an existing resource, such as by giving a name another resource already has.
- `410` — The resource the request names is missing or has expired.
- `500` — Roboto reported an error that this release of the SDK cannot match to a specific exception class. Reported for an element of a :py:class:\`\~roboto.http.BatchResponse\` whose error names a code this release defines no class for, or that arrived without a code, without a message, or as text that is not an error envelope at all. It carries whatever code and message Roboto sent, so a caller handling the failure still learns what went wrong; when no message could be read, the message is the error's raw text. :py:meth:\`\~roboto.domain.devices.Device.create\_session\` raises it, and :py:meth:\`\~roboto.domain.devices.Device.create\_sessions\` lists it in the batch's :py:attr:\`\~roboto.http.BatchResponse.failed\`. The error envelope carries no status code, so \`\`http\_status\_code\`\` reports the 500 inherited from \`\`RobotoDomainException\`\` rather than the status the failure had.
- `501` — The request asks for an operation this deployment of Roboto does not provide.
- `503` — Roboto could not accept the request, such as under heavy load. Retrying later may succeed.
- `504` — Roboto ran out of time while processing the request. Retrying may succeed.
- `507` — The response to the request is larger than Roboto can send. Retrying the same request fails the same way; request less data at a time.

Response example, 200:

```json
{
  "data": {
    "restricted": true,
    "grants": [
      {
        "subject": {
          "kind": "user",
          "id": null
        },
        "role": "viewer"
      }
    ]
  }
}
```
