---
title: "Read what one account may do"
type: reference
method: GET
path: /rest-api/system-users/{userId}/access.do
tag: "Users"
---

# Read what one account may do

`GET https://YOUR-NETWORK-DOMAIN/rest-api/system-users/{userId}/access.do`

The account's role, whether it is switched on, the admin console pages it opens and the permissions it actually holds. 'permissions' is the account's own permission map, each row of the matrix it holds something on, with the granting type each permission is set to ('view-all', 'create-enabled', and for a row that is simply on or off the granting type alone). A row the account holds nothing on is left out, so this is what it may do rather than the whole catalogue -- read the role for that. 'roleManageable' says whether the caller may change that role and hand it to an account; the role is changed with user/update.do and its permissions with roles/{roleId}.do. No password, API key or other credential is part of this answer, and none can be read or set through it. Requires the User Management console permission and the right to see users of that account's role.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `userId` | integer | yes | `42` | Numeric id of the user, as system-users/search.do reports it |

## Responses

- `200` — {success, userId, username, email, firstName, lastName, active, created, role, adminPages, permissions, roleManageable}
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — The caller does not hold User Management, or may not see users of that role
- `404` — No user with that id

## Example request

```bash
curl --request GET \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/system-users/42/access.do' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/users/get-system-users-access