[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Enroll users in courses

> Enroll users in one or more courses with a start date and a due date. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/ispring/enroll_users

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Enroll users in one or more courses with a start date and a due date.

iSpring Learn (iSpring LMS) MCP tools: https://cotlet.dev/docs/mcp/ispring.md

MCP tool: `ispring_write → enroll_users`

Access: write. Confirm: waits for the user's OK before it runs.

Runs the Enroll Users wizard: courses, users, then parameters. due_mode is use_course_settings (the Availability tab of the course), by_date (midnight of due_date unless a time is given), for_period (due_period counted from the start) or none. In for_period a month is always 30 days and a year 365. Learners get a notification in the user portal and by email, and the course appears in My Courses. Department Administrators can enroll only users from their departments. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `course_ids` | string[] | yes | Courses from list_courses. |
| `user_ids` | string[] | yes | Users from list_users. |
| `start_date` | datetime | no | When the course opens. Default: now. |
| `due_mode` | enum | no | use_course_settings (default), by_date, for_period or none. |
| `due_date` | date | no | Needed for by_date. |
| `due_period` | string | no | Needed for for_period: a number and days, weeks, months or years, e.g. "30 days". |
| `restrict_access_after_due` | boolean | no | With by_date or for_period: learners cannot study after the due date. Default: false. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ispring_write",
    "arguments": {
      "operation": "enroll_users",
      "arguments": {
        "course_ids": [
          "c_4f2a91"
        ],
        "user_ids": [
          "u_81c2d4",
          "u_81c2e9"
        ],
        "start_date": "2026-11-02T09:00",
        "due_mode": "by_date",
        "due_date": "2026-11-30"
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "enrolled": 2,
    "enrollments": [
      {
        "enrollment_id": "e_70a1b3",
        "user": "Ana Lopez",
        "course": "Information Security Basics",
        "start_date": "2026-11-02T09:00:00",
        "due_date": "2026-11-30T00:00:00"
      },
      {
        "enrollment_id": "e_70a1b4",
        "user": "Tom Becker",
        "course": "Information Security Basics",
        "start_date": "2026-11-02T09:00:00",
        "due_date": "2026-11-30T00:00:00"
      }
    ]
  },
  "isError": false
}
```

Previous: [Get learner progress report](https://cotlet.dev/docs/mcp/ispring/get_learner_progress.md)
Next: [Cancel enrollments](https://cotlet.dev/docs/mcp/ispring/cancel_enrollment.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.