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

# Project linking

> Connect a client project to a Business Workspace with a one-time key and explicit delegated permissions.

Project linking lets a technical owner delegate selected management work to a Business Workspace without sharing an AvraAPI account, project secret, or payment gateway credential.

## The connection flow

<Steps>
  <Step title="Technical owner creates a Connect Key">
    From the project dashboard, the technical owner creates a one-time Workspace Connect Key and selects which categories can be delegated.
  </Step>

  <Step title="Owner shares the key securely">
    Send the key only to the intended Workspace owner or authorized manager. It is time-limited and should be treated as sensitive until redeemed.
  </Step>

  <Step title="Business Workspace redeems the key">
    The receiving Workspace redeems the key. The project becomes connected to that Workspace and the selected permissions are stored with the project connection.
  </Step>

  <Step title="Workspace members operate within two boundaries">
    A member needs both the relevant Workspace role permission and the technical owner’s delegated project permission.
  </Step>
</Steps>

## Delegated categories

| Delegation | Allows the Workspace to manage |
| - | - |
| Advanced services | UPG slot attachment/release and approved UPG configuration work |
| Providers | Standard project provider configuration |
| API credentials | Project credential generation and rotation |

Delegation does not give the Workspace authority to delete the client project or remove the technical owner’s access.

## Disconnect or exit safely

The technical owner can return a connected project to their Personal Workspace. If the project has an active UPG slot, the exit flow requires explicit consent because it releases the slot back to the Business Workspace’s available capacity.

On a successful exit:

* the project returns to the technical owner’s Personal Workspace;
* delegated permissions are cleared;
* pending Connect Keys are revoked; and
* active UPG project attachments are released.

<Warning>
  Releasing a slot blocks new payment checkout immediately. It does not retroactively cancel a payment session that was already created; its signed completion context may still be completed safely.
</Warning>

## When a Workspace is deactivated

Deactivating a Business Workspace does not delete customer projects. Internal projects return to the Workspace owner’s Personal Workspace, while delegated external projects return to each project’s technical owner. Delegation is removed and active UPG attachments are released.


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