> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Users Guide

> How to list the people in a workspace, for example to reconcile seats with your other tools

## Overview

`GET /v1/users` lists the people in your workspace: admins and members, whether or not they send from an identity. Use it to keep a seat inventory of Enginy next to your other tools.

## Who can call it

* The API key needs the `USERS_READ` scope, or `ALL`. `USERS_READ` is read-only and grants nothing else.
* The key must have been created by a workspace admin. A key created by a member gets `403`. Over MCP, connect as a workspace admin.

## List users

```bash theme={null}
curl "https://openapi.enginy.ai/v1/users?page=1&pageSize=100" \
  -H "x-api-key: $ENGINY_API_KEY"
```

```json theme={null}
{
  "data": [
    {
      "id": 1234,
      "name": "Ada Lovelace",
      "email": "ada@acme.com",
      "role": "admin",
      "status": "active",
      "createdAt": "2026-01-05T09:00:00.000Z",
      "lastActiveAt": "2026-11-14T00:00:00.000Z"
    }
  ],
  "meta": { "page": 1, "pageSize": 100, "total": 52 }
}
```

| Field | Notes |
| - | - |
| `id` | The user ID. |
| `role` | `admin` manages members, roles and billing. `member` is everyone else, whatever their role. |
| `status` | Always `active`: the list holds the current members. |
| `lastActiveAt` | The last day the user opened Enginy (UTC), or `null` if never. Useful to spot unused seats. |

Filter with `role=admin` or `role=member`, and with `search` (name or email). Page with `page` and `pageSize` (at most 100); `meta.total` is the number of users that match.

## Who is listed

Every current admin and member of the workspace. These are not listed:

* Pending invitations. A person appears once they accept.
* Removed users.
* Enginy staff with access to your workspace.
* Staff of an organization (agency) who manage your workspace from that organization.
* CRM owners that Enginy keeps for task assignment. List those with `GET /v1/tasks/owners`.

## Users and identities

A user is a person who logs in to Enginy. An identity is a sending account (LinkedIn, email) that users send from. A user may send from no identity, and several users can share one.

The workspace capacity counts identities, not users: `GET /v1/workspace` returns `identities.used` and `identities.max`. The number of users can therefore differ from what the workspace is billed for. To list the sending accounts, use `GET /v1/identities`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.