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

# Plans & capacity

> Understand Workspace UPG entitlements, project activation slots, upgrades, and safe release behavior.

UPG commercial access belongs to a Workspace. A project consumes one active project activation slot only when the Workspace explicitly attaches it.

## Capacity is not a credential

A UPG slot is not an API key and does not create a second project identity. The application continues to authenticate with the project’s normal AvraAPI credentials.

<CardGroup cols={3}>
  <Card title="Workspace Entitlement" icon="building" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    Includes the base capacity and any optional extra capacity.
  </Card>

  <Card title="Project Attachments" icon="link" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    Active UPG project slots attached to connected projects.
  </Card>

  <Card title="Gateway Configurations" icon="vault" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    The project's own encrypted gateway credentials.
  </Card>
</CardGroup>

## Attach a project

An authorized Workspace member selects an eligible connected project and attaches an available slot. In the same protected operation, AvraAPI validates the entitlement and creates or resumes the project’s UPG integration anchor.

The project still needs an active gateway configuration before it can start a checkout.

## Release a project slot

Releasing a slot immediately prevents **new** checkout creation for that project. The project’s encrypted configurations are retained so the same project can be reattached later without re-entering credentials.

An already-created payment session can still complete through its signed, project-bound completion context. This avoids abandoning a customer who was already redirected to a provider.

## Plan changes

A Workspace has one active UPG base entitlement at a time. Changes can include a first plan activation, a billing-cycle change, an upgrade, added capacity, or a scheduled downgrade.

| Situation | Safe behavior |
| - | - |
| Add capacity | The server recalculates the current quote and adds available project capacity after payment succeeds. |
| Downgrade | It is scheduled at the end of the paid term and cannot reduce capacity below active project attachments. |
| Upgrade | Any eligible unused-term value is applied through a server-calculated quote, not as a browser-calculated refund. |
| Deactivate Workspace | Active entitlements are cancelled, slots are released, and eligible unused credit is handled by the Workspace deactivation flow. |

<Info>
  Gateway access is plan-aware. A configured gateway that is outside the current entitlement is not available for new checkout until the Workspace plan permits it.
</Info>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.