> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runchat.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Subscriptions & Credits

> Share a Runchat subscription with your team to give members access to its features and a shared credit pool. Supports per-member seat types and credit limits.

## Sharing your subscription

When you create a new team, your subscription will automatically be assigned to the team so that members can access seats and credits.
If you do not wish to share seats and credits with the team, click "Remove Subscription" from the [team page](https://runchat.com/dashboard/team) header.
To re-assign your subscription, click **Assign Subscription to Team**.

To add or remove seats, click **Manage Subscription** to open the Stripe billing portal.

<Info>Only subscription owners can manage subscriptions.</Info>

## Subscription access

You can assign different types of access to your subscription to individual members of the team.

| Type         | Features                  | Credits              |
| ------------ | ------------------------- | -------------------- |
| **Seat**     | Team subscription         | Shared team pool     |
| **Credits**  | Member's own subscription | Shared team pool     |
| **Personal** | Member's own subscription | Member's own credits |

* **Seat** allows members to draw from the teams shared credit pool and all features on the team plan (e.g. private workflows and model whitelists on Pro)
* **Credits** allow members to draw from the team's shared credit pool. Access to subscription features (e.g. privacy, save history, whitelist) is determined by the member's individual subscription.
* **Personal** is for members who use their own subscription and credits entirely. They can still access team workflows and collaborate.

You can change seat types from the members table on the team page, or use the bulk actions toolbar to update multiple members at once.

## Credit pool

When a subscription is assigned to the team, all credits are pooled:

> **Total credits** = (monthly credits per seat × number of seats) + purchased credits + rollover credits

By default, all members with a **Seat** or **Credits** seat type share this pool. You can set per-member credit limits from the members table to cap individual usage and keep spending equitable.

## Switching to Personal access after exhausting team credits

You can use Runchat's team system to allocate a fixed credit budget to all team members, and then allow members to continue working within the team using their own individual subscriptions or topup-credits.
In this scenario, initially assign all members of the team access to a seat or the credit pool. Optionally assign user's individual credit limits as required.
When the team member exhausts this credit limit, they (or the team admin) can update their access to "Personal" from the team dashboard.
They will then be able to continue participating in the team but will use their own subscription's credits.
Members can opt back in to the team credit pool at any time.

## Unassigning a subscription

To stop sharing your subscription with the team, click **Remove My Subscription** from the team page header. This unlinks the subscription and removes all seat assignments. Members who were assigned a seat will fall back to using their Personal subscription.

Only the subscription owner can unassign it.

## Next steps

* [Teams](/concepts/teams/teams): roles, invites, and collaboration
* [Model whitelist](/concepts/teams/model-whitelist): restrict which models the team can use
* [Credits](/concepts/credits): how individual credits work outside a team context