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

# Roles and access

> The parties in an Already transaction and what each can see.

One person can have more than one workspace. The portal shows workspaces assigned to the authenticated account; selecting a workspace does not change the signed-in identity.

| Role | What it does | What it can see |
| - | - | - |
| Partner platform | Submits approved invoice or payment data through the partner API; receives lifecycle events | Its own submissions, obligations, API clients, and webhook status |
| Business / end customer | Holds the receivable and chooses whether to get paid early | Its enrolled invoices, offers, payout destination, and payment status |
| Payer / obligor | Owes the original payment on its normal due date | Obligations naming that payer and its own repayment actions |
| Capital provider | Commits money to a funding pool, subject to verification | Available pools and **its own pool positions**, not individual business invoices or payouts |
| Already operator | Reviews intake, publishes offers, monitors transfers and repayments, manages access | Operational records according to admin permissions |

An **obligation** is the payer's amount due to the business. An **offer** is Already's optional proposal to advance part of it. A **funding pool** holds committed capital for a program. An offer is only available to the business after an operator approves it.

Partner API bearer keys authenticate software, not people. A signed-in portal session does not grant a partner API key, and an API key does not grant portal admin access. See [connections](https://docs.already.finance/integrate/connections.md).


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