List users (members) with roles and teams

# Instructions — Listing users (members)

## ⚠️ Roles and teams not available

`get_users` returns: `id`, `firstName`, `lastName`, `email`, `companyId`

**What is NOT available:**
- Role (admin, controller, employee...)
- Team / department
- Hire or departure date

→ To filter "the admins" or "the managers": not possible via `get_users` alone.
→ Solution: use cost centers or analytical fields as an organizational proxy.

## ⚠️ Archived users: firstName and lastName = null

Archived users have neither a first name nor a last name — only `id` and `email` are present.

```json
// Active user:
{ "id": "...", "firstName": "Alice", "lastName": "Martin", "email": "alice@spendesk.com" }

// Archived user:
{ "id": "...", "firstName": null, "lastName": null, "email": "alice@spendesk.com" }
```

→ Always use `email` as a fallback label if `firstName=null`.
→ Recommended display format: `firstName + lastName || email`

## ⚠️ 1200-second cache (20 minutes)

Data can be up to 20 minutes stale.
→ For real-time needs (ongoing onboarding, recent departure), inform the user.

## Step 1 — List active users

```json
{ "companyId": "...", "status": "active", "pageSize": 100 }
```

Always paginate until `hasNextPage=false` — this account has more than 10 active users (hasNextPage=true as soon as pageSize=10).

## Step 2 — Include archived users (historical audit)

```json
{ "companyId": "...", "status": "archived", "pageSize": 100 }
```

Usage: retrieve past expenses of a former employee (by email or userId).
⚠️ `firstName`/`lastName` are null — display only the email or ID.

## Step 3 — Resolving a userId into a name

To resolve a `memberId` (from a payable) into an employee name:
1. Call `get_users` (status=active)
2. If not found, call `get_users` (status=archived)
3. Display: `${user.firstName} ${user.lastName}` if not null, otherwise `user.email`

## Step 4 — Use as a reference for spendesk_analyze_spend

To filter spend by employee:
1. `get_users` → find the `userId` by first name/email
2. Pass `filters.employeeIds=[userId]` in `spendesk_analyze_spend`

## Live example (real data)

- Active users: > 10 (hasNextPage=true at pageSize=10)
- Archived users: > 5 (hasNextPage=true at pageSize=5)
- Confirmed archived format: `{ firstName: null, lastName: null, email: "nina.mayer@spendesk.com" }`

## Example prompt

- "List all active employees" → status=active + full pagination
- "Find the expenses of Nina Mayer (former employee)" → status=archived, filter by email
- "Who has the most expenses in June?" → get_users + spendesk_analyze_spend groupBy=employee