[pablito25sp]

Summary

Organization.invite_users calls inviteMembers in groups of 100 addresses. Each address gets one result, in the original order. An address longer than 320 characters does not stop the other addresses.

Release this SDK change after inviteMembers is deployed.

Jira: PLT-4659
Jira: PLT-4608
Jira: PLT-4609

---

Note

Medium Risk
Adds org membership invitation flows and role assignment; behavior depends on new backend inviteMembers, though existing single-invite APIs are unchanged.

Overview
Adds Organization.invite_users for inviting many addresses in one call, backed by the inviteMembers mutation. Callers get an ordered List[InviteResult] with InviteMemberStatus per address (invited, already member, seat limit, invalid email, etc.), including optional reason and invite_id.

Supports workspace-wide org roles or the same project/group role across optional projects and user_groups (objects or ids). The client batches up to 100 addresses per request, blocks over-long emails locally (320 chars), and marks cross-batch duplicates as DUPLICATE so one bad address does not fail the rest. InviteMemberStatus, InviteResult, and invite docs are exported and documented; unit tests cover payloads, batching, validation, and edge cases.

Note: Intended for use after the inviteMembers API is deployed on the server.

^{Reviewed by Cursor Bugbot for commit 682cb5c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Current version of PR was reviewed by /review-bugbot on Oct 16, 15:13 GMT-3. It flagged 0 findings.

^{Bugbot on commit fb72bd4 is skipped.}