> For the complete documentation index, see [llms.txt](https://docs.vomevolunteer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vomevolunteer.com/resources/schedule/shift-series/write-operations/assign-users-to-a-shift-series.md).

# Assign users to a shift series

Assigns one or more users to one or more series. Every user is assigned to every series listed.

This is not the same promise as [assigning to a shift](https://docs.vomevolunteer.com/resources/schedule/shifts/write-operations/assign-users-to-shifts.md). A shift assignment books one date. A series assignment is a standing commitment: the volunteer is booked onto every future occurrence, and occurrences Vome creates later pick them up automatically. Use this for "Tuesdays are Priya's" and the shift endpoint for a single date.

#### Endpoint

`POST /api/shift-series/bulk-assign/`

### Fields

| Field          | Required | Description                                                                                                                                              |
| -------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `series_ids`   | Yes      | Up to 100 series.                                                                                                                                        |
| `user_ids`     | Yes      | Up to 500 users. Each is assigned to each series.                                                                                                        |
| `joined_at`    | No       | ISO datetime. Defaults to now, so nobody is retroactively recorded as having attended shifts that already happened. Pass a date to start them from then. |
| `notify_users` | No       | Defaults to `false`.                                                                                                                                     |
| `message`      | No       | A short note included in the notification.                                                                                                               |

### What assignment does besides creating rows

Fanning a volunteer out across a series is not a simple insert. Vome also:

* skips occurrences where the volunteer has booked time off
* clones any form requirements that are due on reserving
* schedules the reminder chain on each shift
* builds the roster snapshot when guests are involved
* removes the volunteer from any matching waitlist entries

#### Payload sample

```json
{
  "series_ids": ["7c0f3f20-6e39-4b80-bb35-7d743f0193a6"],
  "user_ids": [
    "4a17144c-58c8-4103-8c0a-f2ac12079e7a",
    "06d9d2da-e99d-4c9a-9f95-c9acd55e9ee1"
  ],
  "notify_users": true,
  "message": "Thanks for taking Tuesdays and Thursdays."
}
```

#### Response sample

```json
{
  "success": true,
  "processed": 1,
  "assignments": [
    {
      "series_id": "7c0f3f20-6e39-4b80-bb35-7d743f0193a6",
      "series_enrollments_created": [
        "3b4e9461-8b34-4d5b-9c3d-48f6f85f0f01",
        "61a1f40d-1f5a-49f0-b3e7-34ac3f5dc6d7"
      ]
    }
  ],
  "errors": {}
}
```

### If the opportunity requires approval

On an opportunity set to request-to-book, a series enrollment lands as pending approval rather than active, and is approved in Vome.
