curl -X POST "https://api.example.com/v1/cases/{case_id}/collaborators" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "john@example.com",
    "first_name": "John",
    "last_name": "Johnson",
    "role": "editor",
    "permissions": {
      "can_manage_documents": true,
      "can_manage_financials": true,
      "can_manage_probate": false,
      "can_manage_collaborators": false,
      "can_use_tools": true
    },
    "message": "Hi John, I am sharing access to Grandpa Vernen estate case with you."
  }'

Owner sends invite  ->  Status: pending
                        (email sent to collaborator)

Collaborator accepts ->  Status: accepted
                         (case appears in their dashboard)

Collaborator declines -> Status: declined

Owner revokes access ->  Status: revoked
                         (DELETE endpoint)

curl "https://api.example.com/v1/cases/{case_id}/collaborators"```

### Update a collaborator's role or permissions

```bash
curl -X PATCH ".../collaborators/{collaborator_id}" \
  -H "Content-Type: application/json" \
  -d '{
    "role": "viewer",
    "permissions": {
      "can_use_tools": false
    }
  }'

curl -X POST ".../collaborators/{collaborator_id}/resend"```

### Remove a collaborator

```bash
curl -X DELETE ".../collaborators/{collaborator_id}"```

## How Collaborators See Shared Cases

When a collaborator accepts an invite, the case appears in their `/users/me/cases` listing with their assigned role:

```json
{
  "data": [
    {
      "id": "01K5WF06MJ6T99HRYE78AN7XM8",
      "deceased_name": "John Jonas Johnson",
      "role": "editor",
      "estate_value": "unknown",
      "flow_position": "Closure - Decisions - Initial"
    }
  ]
}