> For the complete documentation index, see [llms.txt](https://pool-party-xyz.gitbook.io/pool-party-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/resources/glossary.md).

# Glossary

* **Pool:** an on-chain container for a strategy.
* **Mandate:** the immutable rules a pool follows (allowed assets, limits, exposures).
* **Manager:** the party operating a pool's strategy (a person; AI agents coming soon).
* **User:** someone who takes part in a pool by depositing.
* **Share:** the contract's internal unit that measures your participation. Not a token.
* **NAV:** the total value of a pool's positions.
* **Adapter:** a standardized integration that connects the pool to an asset or protocol.
* **Self-custody:** your right tied to your wallet; no one else can access it.
* **Smart account:** an account with account abstraction (ERC-4337); today, social login.
* **Performance fee:** a fee charged on a pool's gains.
* **Swap fee:** a fee to convert USDC into the pool's assets and back.
* **In kind:** withdrawing in the strategy's assets, without converting to USDC.
* **On-ramp / Off-ramp:** buying crypto with fiat / cashing out to fiat and topping up crypto cards.
* **Quacks:** the points in the Rubber Rush program.

***

***

***

Plain-language definitions of terms used across the platform. Click any entry to expand it.

***

## A — F

<details>

<summary><strong>API key</strong></summary>

A secret token that authenticates requests to the platform's API. Keys are scoped to a workspace and inherit the permissions of whoever created them. See [Deposits & Self-custody](/pool-party-docs/pool-party-v2-docs/core-concepts/deposits-and-self-custody.md).

</details>

<details>

<summary><strong>Automation</strong></summary>

A piece of code that runs in response to a trigger — for example, a deploy completing or a comment being posted. See [For Managers](/pool-party-docs/pool-party-v2-docs/for-managers/for-managers.md).

</details>

<details>

<summary><strong>Build</strong></summary>

The process of turning your source code into deployable output. Each build produces an artefact, which is then promoted to a deploy.

</details>

<details>

<summary><strong>Custom domain</strong></summary>

Your own domain (like `docs.yourcompany.com`) attached to a project, in place of the auto-generated subdomain. See [For Users](/pool-party-docs/pool-party-v2-docs/for-users/for-users.md).

</details>

<details>

<summary><strong>Deploy</strong></summary>

A live version of your project, served from a URL. Each successful build can be promoted to a deploy. The current production deploy is the one served at your primary URL.

</details>

<details>

<summary><strong>Environment</strong></summary>

The set of variables, secrets, and configuration that applies when your project runs. Most projects have at least two environments: production and preview.

</details>

***

## G — P

<details>

<summary><strong>Guest</strong></summary>

A workspace role that can view published deploys but nothing else. Guests don't count towards your member limit. See [Deposits & Self-custody](/pool-party-docs/pool-party-v2-docs/core-concepts/deposits-and-self-custody.md).

</details>

<details>

<summary><strong>Member</strong></summary>

Anyone with access to a workspace. Each member has a role that determines what they can do. Different from a guest, which is a special role that doesn't count towards your member limit.

</details>

<details>

<summary><strong>Preview deploy</strong></summary>

A deploy created automatically for a branch or pull request, served at a unique URL. Used to test changes before they reach production.

</details>

<details>

<summary><strong>Project</strong></summary>

A deployable unit. Each project has its own source, builds, deploys, environment, and domains. Projects are isolated from each other within a workspace. See [Managers & Strategies](/pool-party-docs/pool-party-v2-docs/core-concepts/managers-and-strategies.md).

</details>

***

## R — Z

<details>

<summary><strong>Role</strong></summary>

A workspace-level designation that determines what a member can do. Roles are: Guest, Viewer, Reviewer, Editor, and Admin. See [Deposits & Self-custody](/pool-party-docs/pool-party-v2-docs/core-concepts/deposits-and-self-custody.md).

</details>

<details>

<summary><strong>Source</strong></summary>

The repository or upload that produces your project's builds. A project has exactly one source.

</details>

<details>

<summary><strong>SSO</strong></summary>

Single sign-on. Lets your team authenticate with your identity provider (Okta, Azure AD, etc.) instead of platform-specific credentials. Available on Business and Enterprise plans.

</details>

<details>

<summary><strong>Trigger</strong></summary>

The event that starts an automation — for example, `deploy.succeeded` or `webhook.received`. See [For Managers](/pool-party-docs/pool-party-v2-docs/for-managers/for-managers.md).

</details>

<details>

<summary><strong>Workspace</strong></summary>

The top-level container for a team's work. Owns billing, members, and projects. See [Managers & Strategies](/pool-party-docs/pool-party-v2-docs/core-concepts/managers-and-strategies.md).

</details>

***

{% hint style="info" %}
A term missing? [Suggest it in the community](https://community.example.com/) — we update this glossary regularly.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/resources/glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.