---
title: "Multi-use invites & seat pools — Teams for Laravel | Roundly"
description: "Issue invite links usable N times or without limit, track consumed and remaining seats, and audit exactly who joined through each link."
url: https://roundly-consulting.com/open-source/docs/teams-for-laravel/seat-pools
language: en
---

[All packages](https://roundly-consulting.com/open-source.md)

[Teams for Laravel](https://roundly-consulting.com/open-source/docs/teams-for-laravel.md)

# Multi-use invites & seat pools

Pass maxUses to turn an invite into a seat pool — a link usable up to N times. null makes it unlimited; the default is 1 (single use):

```php
$invite = Teams::for($team)->invites()->create(role: 'member', maxUses: 5);
// ... three people accept ...

$invite->consumedSeats();      // 3
$invite->remainingSeats();     // 2 (null when unlimited)
$invite->hasRemainingSeats();  // true
$invite->isExhausted();        // false

// Unlimited seats:
$link = Teams::for($team)->invites()->create(role: 'member', maxUses: null);
```

| Method | Returns | Meaning |
| --- | --- | --- |
| `consumedSeats()` | int | How many times the invite was accepted (uses). |
| `remainingSeats()` | ?int | max\_uses − uses, never below 0; null when unlimited. |
| `hasRemainingSeats()` | bool | True when unlimited or at least one seat is left. |
| `isExhausted()` | bool | uses ≥ max\_uses; always false when unlimited. |
| `acceptedMembers() / consumers()` | HasMany<Member> | The members who joined through this invite. |

## The seat ledger

Every accept stamps the membership’s accepted\_invite\_id, so the invite knows exactly who consumed each seat. The roster is a regular relation — eager-load or paginate it:

```php
$invite->acceptedMembers;                              // Collection<Member> — who used a seat
$invite->consumers();                                  // readable alias of acceptedMembers()
$invite->acceptedMembers()->with('member')->paginate(20);

// From the member side:
$member->acceptedInvite;   // the Invite this member joined through, or null
```

Force-deleting or hard-pruning an invite nulls accepted\_invite\_id on its members instead of deleting them, so the membership roster is never lost to invite cleanup. Re-adding an active member never rewrites the invite they originally joined through.

## Show your open-source love

This package is free and MIT-licensed. If it saves you time, a one-off donation or a Patreon membership keeps it maintained, tested and documented.

[More ways to support, including crypto](https://roundly-consulting.com/support-us.md)

By donating, you agree to our [donation terms](https://roundly-consulting.com/donation-terms.md).

[Support our open source work (opens in a new tab)](https://donate.stripe.com/dRmeVe8FX5PF1Qd9pXcEw00) [Join us on Patreon (opens in a new tab)](https://www.patreon.com/cw/roundly)

## Want this built into your product?

We integrate our packages into custom Laravel and AI builds. Tell us what you're working on and we'll reply within 48 hours.

[Get a quote in 48 hours](https://roundly-consulting.com/contact.md) [Browse all packages](https://roundly-consulting.com/open-source/docs/teams-for-laravel.md)