Provisioning

BusinessMode supports several distinct ways to allocate access: direct seat assignment, bulk roster operations, Customer Invitations, Access Codes, and delegated Organization administrators. They are not interchangeable credentials or workflows.

Direct assignment identifies an external user immediately. Bulk roster previews or processes many external IDs against a License. A Customer Invitation is a bearer invitation delivered into a customer-user workflow; creating it does not reserve a seat. Redemption by your customer backend supplies the token and externalUserId, then performs the canonical License and Workspace-capacity checks. Recipient email is not the external user ID. The invitation snapshots its destination URL when created, so later Project Settings changes do not rewrite existing invitations or pending email deliveries.

An Access Code is a separate bearer credential redeemed by your customer backend. Its redemption limit counts lifetime successful unique users per code. Reusing an existing active assignment still consumes a new user's code redemption; releasing a seat does not restore code capacity. This limit is separate from License seatLimit.

An Organization administrator is an authenticated BusinessMode human with delegated Organization portal authority, not a customer end user.

Inspect redeem Invitation, redeem Access Code, bulk roster preview, and portal Organizations. See Authentication before integrating a bearer path.