> ## 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.

# Workspace overview

> Use Workspaces to manage teams, connected projects, UPG capacity, and delegated access without sharing account credentials.

Workspaces give teams a shared operational home without changing who technically owns a project. They are designed for agencies, businesses, and internal teams that need to manage UPG capacity, billing, team access, and approved project operations.

<CardGroup cols={2}>
  <Card title="Personal Workspace" icon="user" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    Every account has one Personal Workspace. New projects belong here by default.
  </Card>

  <Card title="Business Workspace" icon="building" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    A shared Workspace for a team, agency, or business to manage approved work.
  </Card>
</CardGroup>

## Two layers of project ownership

Every project has a **technical owner** and a **management Workspace**. These are intentionally different responsibilities.

| Layer | What it means | What it protects |
| - | - | - |
| Technical owner | The user who created the project | Core project control, including access, updates, pause, and deletion |
| Management Workspace | The Workspace currently responsible for approved commercial and operational work | Team collaboration, UPG plans, slot allocation, and delegated services |

The technical owner never loses access merely because a project is connected to a Business Workspace.

## How a connected project works

Project linking uses a time-limited Workspace Connect Key. The technical owner chooses exactly what the Business Workspace may manage before the key is redeemed.

<Steps>
  <Step title="Create a Connect Key">
    The technical owner creates a Connect Key.
  </Step>

  <Step title="Choose permissions">
    The owner chooses delegated project permissions.
  </Step>

  <Step title="Redeem the key">
    The Business Workspace redeems the key.
  </Step>

  <Step title="Project connected">
    The project is successfully connected to that Workspace.
  </Step>

  <Step title="Managed access">
    Workspace members act only within role and delegated permission limits.
  </Step>
</Steps>

For example, a client can allow an agency to configure UPG gateways while refusing permission to rotate project API credentials.

<Tip>
  Workspace role permissions and project delegation are both required. A team member needs permission from their Workspace role, and the connected project must also have delegated that category to the Workspace.
</Tip>

## Team roles and invitations

Workspace Owners can invite members, assign default or custom roles, and apply granular permissions. An invitation creates a pending invitation first; membership becomes active only when the invited AvraAPI account accepts it.

The Workspace owner bypasses normal Workspace permission checks. Other members receive only the permissions assigned by their role.

## UPG capacity and connected projects

UPG plans belong to the Workspace, while encrypted gateway configurations belong to the individual project. A project must have an active Workspace UPG slot before it can create new payment checkout sessions.

This separation means an agency can manage its Workspace capacity without ever receiving a customer's gateway secret.

<CardGroup cols={3}>
  <Card title="Connect projects" icon="link" href="/workspaces/project-linking" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    Learn about Connect Keys, delegation, and safe project exit.
  </Card>

  <Card title="Roles & permissions" icon="shield" href="/workspaces/roles-and-permissions" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    Understand the layered authorization model.
  </Card>

  <Card title="Plans & capacity" icon="layer-group" href="/workspaces/plans-and-capacity" className="border-2 border-slate-800/60 hover:border-[#0450ff] transition-all duration-700 ease-out">
    Learn how UPG entitlements and project slots work.
  </Card>
</CardGroup>


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