zuplo 7.9.5 → 7.9.8

package/docs/ai-gateway/usage-limits.mdx

@@ -2,40 +2,43 @@
 title: "Usage Limits & Budget Rules"
 sidebar_label: "Usage Limits"
 description:
-  Set spending, token, and request budgets at the gateway, team, and app levels,
+  Set spending, token, and request budgets at the gateway, pool, and app levels,
   and give every metadata value its own separate budget using expression rules.
 ---
 
-Set spending, token, and request budgets for your apps, teams, and gateway to
+Set spending, token, and request budgets for your apps, pools, and gateway to
 control how much they can use.
 
 ## Budget Hierarchy
 
 Limits at every level apply together. The gateway checks its own limits, parent
-team limits, and app limits. An exhausted **Block** limit rejects the request
+pool limits, and app limits. An exhausted **Block** limit rejects the request
 unless the normal provider path uses a configured
 [quota fallback](#when-a-limit-is-exceeded). **Warn** limits allow the request
 and report the warning. Budgets cover these levels:
 
 - **Gateway** - Limits across the Zuplo project (for example, $1,000/day),
-  covering all teams, sub-teams, and apps combined
-- **Teams** - Limits covering the team's own usage and every descendant sub-team
-  and app (for example, $500/day for the Engineering team)
+  covering all pools, sub-pools, and apps combined
+- **Pools** - Limits covering the pool's own usage and every descendant sub-pool
+  and app (for example, $500/day for the Engineering pool)
 - **Apps** - Per-app limits for granular control (for example, $10/day for a
   hackathon app)
 
-For example, a team has a $50 monthly shared **Block** budget. App A spends $40
+The [User App](./user-apps.mdx) isn't part of a pool. It has a per-person
+budget, set on the **Users** tab, and gateway limits apply to it as well.
+
+For example, a pool has a $50 monthly shared **Block** budget. App A spends $40
 and App B spends $10. Once that usage is reflected in the budget check, both
-apps have reached the team's budget. Without a quota fallback, requests through
-both apps receive `429 Too Many Requests`. An app outside this team doesn't
-share its $50 budget, but still has its own app, team, and gateway limits.
+apps have reached the pool's budget. Without a quota fallback, requests through
+both apps receive `429 Too Many Requests`. An app outside this pool doesn't
+share its $50 budget, but still has its own app, pool, and gateway limits.
 
 <Diagram direction="vertical" height="h-80">
   <DiagramNode id="gateway" variant="green">
     Gateway · shared budget available
   </DiagramNode>
-  <DiagramNode id="team" variant="red">
-    Team · spent $50 of $50 this month
+  <DiagramNode id="pool" variant="red">
+    Pool · spent $50 of $50 this month
   </DiagramNode>
   <DiagramNode id="appa" variant="red">
     App A · spent $40
@@ -44,28 +47,28 @@ share its $50 budget, but still has its own app, team, and gateway limits.
     App B · spent $10
   </DiagramNode>
   <DiagramNode id="other" variant="green">
-    App outside the team
+    App outside the pool
   </DiagramNode>
-  <DiagramEdge from="gateway" to="team" label="team budget exhausted" />
+  <DiagramEdge from="gateway" to="pool" label="pool budget exhausted" />
   <DiagramEdge
     from="gateway"
     to="other"
-    label="unaffected by this team budget"
+    label="unaffected by this pool budget"
   />
-  <DiagramEdge from="team" to="appa" label="429 without quota fallback" />
-  <DiagramEdge from="team" to="appb" label="429 without quota fallback" />
+  <DiagramEdge from="pool" to="appa" label="429 without quota fallback" />
+  <DiagramEdge from="pool" to="appb" label="429 without quota fallback" />
 </Diagram>
 
-App budgets can add up to more than their team's budget. The team's budget caps
-the combined usage; increasing an app's budget doesn't increase its team's cap.
-The same rule applies to nested teams and the gateway root.
+App budgets can add up to more than their pool's budget. The pool's budget caps
+the combined usage; increasing an app's budget doesn't increase its pool's cap.
+The same rule applies to nested pools and the gateway root.
 
 ## Where limits are configured
 
 | Level   | Budgets                 | Where to configure                                                     |
 | ------- | ----------------------- | ---------------------------------------------------------------------- |
 | Gateway | Shared                  | **Settings → Usage Limits**                                            |
-| Team    | Shared                  | The team's **Usage & Limits** tab                                      |
+| Pool    | Shared                  | The pool's **Usage & Limits** tab                                      |
 | App     | Shared and per-metadata | **Budgets and Costs** in the app's [policy chain](./policy-chains.mdx) |
 
 Use **Budgets and Costs** to set an app's own budget.
@@ -73,7 +76,7 @@ Use **Budgets and Costs** to set an app's own budget.
 :::note
 
 New apps inherit their initial budget settings from their
-[team policy template](./policy-templates.mdx). To limit the team's combined
+[pool policy template](./policy-templates.mdx). To limit the pool's combined
 usage, set a budget on **Usage & Limits**.
 
 :::
@@ -86,7 +89,7 @@ Each budget rule defines who shares the budget and how much they can use.
 
 | Scope           | What it budgets                                             |
 | --------------- | ----------------------------------------------------------- |
-| **Shared**      | One budget for the app, team, or gateway                    |
+| **Shared**      | One budget for the app, pool, or gateway                    |
 | **By metadata** | A separate budget for every distinct value of an expression |
 
 A **By metadata** rule gives each distinct expression value its own allowance.
@@ -133,11 +136,11 @@ again, doesn't reset the period's usage.
 
 <Stepper>
 
-1. Open the [Apps & Teams](https://portal.zuplo.com/+/account/project/ai/apps)
-   tab and select the app.
+1. Open the [Apps](https://portal.zuplo.com/+/account/project/ai/apps) tab and
+   select the app.
 
 1. On the **Policies** tab, configure the **Budgets and Costs** policy (add it
-   from **Add Policy** if the chain doesn't have it).
+   from **Add policy** if the chain doesn't have it).
 
 1. Select **Add rule**, choose the scope, and use **Add limit** to add rows for
    the meters and periods you want to cap. For a **By metadata** rule, enter the
@@ -149,8 +152,8 @@ again, doesn't reset the period's usage.
 
 </Stepper>
 
-The app editor shows team and gateway budgets under **Inherited**. To change
-one, open the team or gateway where you set it.
+The app editor shows pool and gateway budgets under **Inherited**. To change
+one, open the pool or gateway where you set it.
 
 ### Budget expressions
 
@@ -271,19 +274,18 @@ Verdicts name their rule too. A block or warning from a **By metadata** rule
 carries the expression and its `ruleId`; one from an app-wide budget carries
 neither. That's how you tell which rule refused a request.
 
-## Setting team and gateway limits
+## Setting pool and gateway limits
 
-A team budget covers the combined usage of its apps and sub-teams. A gateway
+A pool budget covers the combined usage of its apps and sub-pools. A gateway
 budget covers all apps in the project.
 
-To add a shared team rule, select the team or sub-team in
-[Apps & Teams](https://portal.zuplo.com/+/account/project/ai/teams), then open
-**Usage & Limits**. To add a shared gateway rule, open **Settings → Usage
-Limits**. Both editors use the same meter, period, amount, and action rows as
-the app editor.
+To add a shared pool rule, select the pool or sub-pool in
+[Apps](https://portal.zuplo.com/+/account/project/ai/pools), then open **Usage &
+Limits**. To add a shared gateway rule, open **Settings → Usage Limits**. Both
+editors use the same meter, period, amount, and action rows as the app editor.
 
-The editor shows budgets from parent teams and the gateway under **Inherited**.
-To change an inherited budget, edit it on the team or gateway where you created
+The editor shows budgets from parent pools and the gateway under **Inherited**.
+To change an inherited budget, edit it on the pool or gateway where you created
 it.
 
 ## When a limit is exceeded
@@ -291,7 +293,7 @@ it.
 For a request continuing to a provider, an exhausted **Block** limit uses the
 app's configured **quota fallback** model instead of blocking. See
 [Fallback Models](./fallback.mdx), where the fallback model is selected. This
-applies to gateway and team limits as well as the app's own. The fallback's
+applies to gateway and pool limits as well as the app's own. The fallback's
 usage still counts toward the limits.
 
 Without a quota fallback on that path, the request is rejected with
@@ -314,7 +316,7 @@ Without a quota fallback on that path, the request is rejected with
 ```
 
 The `scope` tells the caller which budget they hit. It is `application` when the
-gateway, a team, or the app exhausts a shared budget. It is `dimension` when a
+gateway, a pool, or the app exhausts a shared budget. It is `dimension` when a
 value exhausts an expression budget. Quote the `ruleId` when raising a support
 request.
 
@@ -330,14 +332,14 @@ the budget check doesn't replace an authentication error with a budget error.
 
 :::caution{title="Budgets fail open by default"}
 
-If a team or gateway budget check fails, the request can continue. However, a
+If a pool or gateway budget check fails, the request can continue. However, a
 failed check doesn't override a budget violation already detected: a cache hit
 still returns `429` if the app's budget check has found an exhausted **Block**
 limit.
 
 To reject requests when **Budgets and Costs** can't complete its own checks,
 enable **Fail closed when metering is unavailable** (`throwOnFailure`). This
-option is off by default and doesn't change how team or gateway check failures
+option is off by default and doesn't change how pool or gateway check failures
 are handled.
 
 :::
@@ -345,7 +347,7 @@ are handled.
 ## Propagation and accounting delays
 
 Budget changes don't take effect immediately. After editing a budget or moving
-an app to another team, allow time for the saved settings and usage totals to
+an app to another pool, allow time for the saved settings and usage totals to
 update. The delay depends on your gateway's
 [cache settings](./policy-chains.mdx#configuration-executor).
 
@@ -354,21 +356,21 @@ spending past a budget before further requests are blocked.
 
 ## Monitoring Usage
 
-Each app, team, and the gateway show current usage against their limits:
+Each app, pool, and the gateway show current usage against their limits:
 
-1. Open the [Apps & Teams](https://portal.zuplo.com/+/account/project/ai/apps)
-   tab and select an app or team
+1. Open the [Apps](https://portal.zuplo.com/+/account/project/ai/apps) tab and
+   select an app or pool
 2. The **Overview** tab shows daily and monthly usage—spend, tokens, and
    requests—with progress against any configured limits
 3. The same tab's **Metrics** frame charts request count, token usage, and cost
    over time; **View in Analytics** opens the full request-level breakdown
-   scoped to that app or team
+   scoped to that app or pool
 
 ## Related Resources
 
 - [Getting Started](../getting-started/ai-gateway/portal.mdx) - Set up your
   first AI Gateway project with budget controls
-- [Managing Teams](./managing-teams.mdx) - Configure team-level budgets
+- [Managing Pools](./managing-pools.mdx) - Configure pool-level budgets
 - [Managing Apps](./managing-apps.mdx) - Configure app-level limits
 - [Fallback Models](./fallback.mdx) - Serve a cheaper model instead of blocking
   when a limit is exceeded

package/docs/ai-gateway/user-apps.mdx

@@ -0,0 +1,166 @@
+---
+title: AI Gateway User Apps
+sidebar_label: User Apps
+description:
+  User Apps let people call your AI Gateway with their own personal API key,
+  each drawing from a personal budget, without creating an app for every user.
+---
+
+A User App lets people call the AI Gateway with their own API key. Instead of
+creating an [app](./apps.mdx) for every person who wants to use AI in their
+everyday tools, everyone with access to the project calls one shared URL with a
+personal key. The gateway knows who made each request, applies that person's
+budget, and reports their usage.
+
+Use an app for software and the User App for people. A support chatbot or a
+nightly batch job is an app, with its own API key, in a [pool](./pools.mdx). An
+engineer using Claude Code or Codex is a person, and calls the User App with a
+personal key.
+
+Each AI Gateway project has one User App, created for you. A new project gets it
+right away; an existing project gets it on its next production deployment. It
+has:
+
+- **A URL** under `/u/`, such as
+  `https://my-gateway-main-2e18f50.zuplo.app/u/741d375d631b429293481d6d0458bb64`.
+  Everyone calls the same URL.
+- **Personal API keys**—each person creates their own. A personal key works only
+  on the User App URL, and an app's API key doesn't work there.
+- **A per-person budget**—an optional spending allowance, such as $50 per day,
+  that applies to each person separately.
+- **A [policy chain](./policy-chains.mdx)**—the policies that run on every
+  request made with a personal key.
+
+The User App isn't part of a pool. Pool budgets and policy templates apply to
+apps; [gateway-wide usage limits](./usage-limits.mdx) apply to both.
+
+## Setting up the User App
+
+Only Admins set up the User App: they choose who can use it, set its budget, and
+edit its policies. With the role-based access control (RBAC) add-on, that means
+project or account **Admins**; Developers, Members, and AI Users can use the
+User App but can't change its budget or policies. Without RBAC, every account
+member is an Admin.
+
+Admins manage the User App on the AI Gateway project's
+[**Users**](https://portal.zuplo.com/+/account/project/ai/users) tab.
+
+<Stepper>
+
+1. **Give people access.** Everyone with a role on the AI Gateway project—Admin,
+   Developer, Member, or AI User—can use the User App.
+
+   With RBAC, to give someone access to the User App and nothing else, open
+   [**Settings** > **Members & Access**](https://portal.zuplo.com/+/account/project/ai/settings/members)
+   on the AI Gateway project, click **Add to project**, enter their email, and
+   choose the **AI User** role. Someone who isn't in your Zuplo account yet is
+   added to it as a **Member**. An AI User can call the User App and see their
+   own keys and usage, but not the rest of the project's configuration or anyone
+   else's usage. See
+   [Managing Project Members](../articles/accounts/managing-project-members.mdx)
+   and [Role Permissions](../articles/accounts/roles-and-permissions.mdx).
+
+1. **Set a per-person budget.** The User App starts with no budget. Open
+   **Budgets** and set how much each person can spend **Per person per day** and
+   **Per person per month**, such as $50 and $100. Each person gets the full
+   amount, counted separately.
+
+   :::caution{title="Set a budget to limit spend"}
+
+   Until you set a budget, the gateway tracks what each person spends through
+   the User App, and **People** shows it, but nothing limits it. A budget you
+   add partway through a day or month counts what each person already spent in
+   that period.
+
+   :::
+
+1. **Review the policies.** **Policies** edits the User App's policy chain, such
+   as which models people can use. The same policies as an app's
+   [policy chain](./policy-chains.mdx) are available.
+
+</Stepper>
+
+**People** lists everyone on the project, how many personal keys each person
+has, and what each person spent today and this month. **Gateway** shows the User
+App's name, which you can change, its configuration ID, and its URL.
+
+### Personal budgets
+
+To give one person a different amount from everyone else, an Admin clicks the
+**Budget** button on the person's row in **People**. **Per day** and **Per
+month** always appear; **Per hour** and **Per week** appear only when the User
+App's budget limits them. For each period, choose:
+
+- **Default**, shown with the User App's amount, such as **Default · $50**. The
+  person's limit follows the User App's amount, including when you change it
+  later.
+- **Custom** to set an amount for this person only, such as $200 per day for a
+  heavy user. Everyone else keeps the User App's amount.
+
+A period that has no User App amount shows **No limit**, and you can't set a
+custom amount for it until you set one on **Budgets**. While anyone has a custom
+amount for a period, you can't remove that period's amount from **Budgets**;
+switch those people back to the default first.
+
+Click **Save** to apply the change. To remove all of a person's custom amounts,
+click **Use all defaults** and confirm. Changing a budget never resets what the
+person has already spent in the current period.
+
+## Using the User App
+
+<Stepper>
+
+1. **Create a personal API key.** Open the AI Gateway project in the Zuplo
+   Portal and go to the
+   [**Home**](https://portal.zuplo.com/+/account/project/ai/home) tab. Under
+   **My API keys**, click **New key**, give it a name such as `Laptop CLI`, and
+   copy the key.
+
+1. **Call the gateway.** Copy the **Gateway URL** shown at the top of the
+   **Home** tab once the gateway has a production deployment—the User App's
+   `/u/` URL—and use it with your personal key in place of the provider's base
+   URL and API key. The **Home** tab also shows setup steps for common tools
+   such as Claude Code and Codex.
+
+</Stepper>
+
+For example, to call the Chat Completions endpoint with `curl`:
+
+```bash
+curl https://my-gateway-main-2e18f50.zuplo.app/u/741d375d631b429293481d6d0458bb64/v1/chat/completions \
+  -H "Authorization: Bearer $ZUPLO_PERSONAL_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "model": "anthropic/claude-sonnet-5",
+    "messages": [{ "role": "user", "content": "Hello" }]
+  }'
+```
+
+The User App serves the same [endpoints](./universal-api.mdx) as an app—**Chat
+Completions**, **Responses**, and **Messages**. The integration guides for
+[Claude Code](./integrations/claude-code.mdx),
+[Codex](./integrations/codex.mdx),
+[Claude Desktop](./integrations/claude-desktop.mdx),
+[GitHub Copilot](./integrations/github-copilot.mdx), and
+[goose](./integrations/goose.mdx) start from your Gateway URL and personal key.
+
+The **Home** tab also shows your allowance and what you've spent against it. If
+no budget is set, it says your requests have no personal spending limit. Once
+you reach your allowance, the gateway refuses requests with
+`429 Too Many Requests` until the period resets or an Admin raises your budget.
+
+## Removing access
+
+A personal key works only while its owner has access to the AI Gateway project.
+When someone loses access to the project, or is removed from the Zuplo account,
+their personal keys for that project are deleted and stop working within
+seconds. You don't need to rotate any keys.
+
+**Additional Resources**
+
+- [Apps](./apps.mdx) - Apps for services and integrations, each with its own API
+  key.
+- [Role Permissions](../articles/accounts/roles-and-permissions.mdx) - Details
+  on the AI User role and other Zuplo account and project roles.
+- [Usage Limits](./usage-limits.mdx) - Gateway-wide limits that apply to every
+  request.

package/docs/articles/accounts/roles-and-permissions.mdx

@@ -3,7 +3,7 @@ title: Role Permissions
 sidebar_label: Role Permissions
 description:
   Compare account, project, and AI Gateway permissions for Admin, Developer,
-  Member, and team roles.
+  Member, AI User, and pool roles.
 ---
 
 <EnterpriseFeature name="Role Based Access Control" />
@@ -11,8 +11,8 @@ description:
 :::note
 
 Without the role-based access control (RBAC) enterprise add-on, every user
-invited to an account is an **Admin**. The **Developer** and **Member**
-distinctions below apply only when RBAC is enabled.
+invited to an account is an **Admin**. The **Developer**, **Member**, and **AI
+User** distinctions below apply only when RBAC is enabled.
 
 :::
 
@@ -46,6 +46,16 @@ The following roles are available at the project level:
   in a project. They can't modify production resources.
 - **Member**: Members of a project can view resources in the project but can't
   modify them.
+- **AI User**: Available only on AI Gateway projects. AI Users can call the
+  project's [User App](../../ai-gateway/user-apps.mdx) with their own personal
+  API keys and see their own usage. They can't view the rest of the project's
+  configuration, other people's keys or usage, or project analytics. There is no
+  AI User role at the account level. To give someone only this access, add them
+  to the AI Gateway project with the **AI User** role from **Members & Access**.
+  Someone who isn't in the account yet joins it as a **Member**.
+
+Every project role, and the account Admin and Developer roles, can also use the
+User App with their own personal API keys.
 
 ## Account Role Permissions
 
@@ -60,10 +70,14 @@ account role.
 |                | View            | ✅    | ✅        | ❌     |
 | AI Providers   | Edit            | ✅    | ❌        | ❌     |
 |                | View            | ✅    | ✅        | ❌     |
-| AI Teams       | Manage          | ✅    | ❌        | ❌     |
+| AI Pools       | Manage          | ✅    | ❌        | ❌     |
 |                | View            | ✅    | ❌        | ❌     |
 | AI Apps        | Manage          | ✅    | ❌        | ❌     |
 |                | View            | ✅    | ❌        | ❌     |
+| AI User App    | Edit            | ✅    | ❌        | ❌     |
+|                | View            | ✅    | ✅        | ❌     |
+| Personal Keys  | Edit (Own Keys) | ✅    | ✅        | ❌     |
+|                | View (Own Keys) | ✅    | ✅        | ❌     |
 | Custom Domains | Edit            | ✅    | ❌        | ❌     |
 |                | View            | ✅    | ✅        | ❌     |
 | Tunnels        | Edit            | ✅    | ❌        | ❌     |
@@ -82,63 +96,78 @@ account role.
 The following table outlines the permissions granted directly by each Zuplo
 project role.
 
-| Resource              | Environment | Action | Admin | Developer | Member |
-| --------------------- | ----------- | ------ | ----- | --------- | ------ |
-| Project               |             | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-| AI Providers          |             | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-| AI Teams              |             | Manage | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ❌        | ❌     |
-| AI Apps               |             | Manage | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ❌        | ❌     |
-| Environment           | Production  | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       |             | Deploy | ✅    | ❌        | ❌     |
-|                       | Preview     | Edit   | ✅    | ✅        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       |             | Deploy | ✅    | ✅        | ❌     |
-|                       | Development | Edit   | ✅    | ✅        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       |             | Deploy | ✅    | ✅        | ❌     |
-| Environment Variables | Production  | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       | Preview     | Edit   | ✅    | ✅        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       | Development | Edit   | ✅    | ✅        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-| Source Control        | N/A         | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-| Members               | N/A         | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-| Custom Domains        | N/A         | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-| Logs                  | Production  | View   | ✅    | ✅        | ❌     |
-|                       | Preview     | View   | ✅    | ✅        | ✅     |
-|                       | Development | View   | ✅    | ✅        | ✅     |
-| Builds                | Production  | View   | ✅    | ✅        | ✅     |
-|                       | Preview     | View   | ✅    | ✅        | ✅     |
-|                       | Development | View   | ✅    | ✅        | ✅     |
-| Analytics             | Production  | View   | ✅    | ✅        | ✅     |
-|                       | Preview     | View   | ✅    | ✅        | ✅     |
-|                       | Development | View   | ✅    | ✅        | ✅     |
-| API Key Buckets       | Production  | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       | Preview     | Edit   | ✅    | ✅        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       | Development | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-| Monetization Buckets  | Production  | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       | Preview     | Edit   | ✅    | ✅        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-|                       | Development | Edit   | ✅    | ❌        | ❌     |
-|                       |             | View   | ✅    | ✅        | ✅     |
-
-The AI Teams and AI Apps rows show project-wide access granted directly by a
-Zuplo account or Zuplo project role. A [team role](../../ai-gateway/teams.mdx)
-can grant additional access to a specific team and its apps, but only when the
-user also has permission to view the associated Zuplo project. A team **Admin**
-can manage the team's settings, members, and apps, while a team **Member** can
+| Resource              | Environment | Action          | Admin | Developer | Member | AI User |
+| --------------------- | ----------- | --------------- | ----- | --------- | ------ | ------- |
+| Project               |             | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ✅      |
+| AI Providers          |             | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+| AI Pools              |             | Manage          | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ❌        | ❌     | ❌      |
+| AI Apps               |             | Manage          | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ❌        | ❌     | ❌      |
+| AI User App           |             | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ✅      |
+| Personal Keys         |             | Edit (Own Keys) | ✅    | ✅        | ✅     | ✅      |
+|                       |             | View (Own Keys) | ✅    | ✅        | ✅     | ✅      |
+| Environment           | Production  | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       |             | Deploy          | ✅    | ❌        | ❌     | ❌      |
+|                       | Preview     | Edit            | ✅    | ✅        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       |             | Deploy          | ✅    | ✅        | ❌     | ❌      |
+|                       | Development | Edit            | ✅    | ✅        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       |             | Deploy          | ✅    | ✅        | ❌     | ❌      |
+| Environment Variables | Production  | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Preview     | Edit            | ✅    | ✅        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Development | Edit            | ✅    | ✅        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+| Source Control        | N/A         | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+| Members               | N/A         | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+| Custom Domains        | N/A         | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+| Logs                  | Production  | View            | ✅    | ✅        | ❌     | ❌      |
+|                       | Preview     | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Development | View            | ✅    | ✅        | ✅     | ❌      |
+| Builds                | Production  | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Preview     | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Development | View            | ✅    | ✅        | ✅     | ❌      |
+| Analytics             | Production  | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Preview     | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Development | View            | ✅    | ✅        | ✅     | ❌      |
+| API Key Buckets       | Production  | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Preview     | Edit            | ✅    | ✅        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Development | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+| Monetization Buckets  | Production  | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Preview     | Edit            | ✅    | ✅        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+|                       | Development | Edit            | ✅    | ❌        | ❌     | ❌      |
+|                       |             | View            | ✅    | ✅        | ✅     | ❌      |
+
+The AI Pools and AI Apps rows show project-wide access granted directly by a
+Zuplo account or Zuplo project role. A [pool role](../../ai-gateway/pools.mdx)
+can grant additional access to a specific pool and its apps, but only when the
+user also has permission to view the associated Zuplo project. A pool **Admin**
+can manage the pool's settings, members, and apps, while a pool **Member** can
 access its apps. AI provider permissions come only from the user's Zuplo account
-or Zuplo project role; team membership doesn't grant provider access.
+or Zuplo project role; pool membership doesn't grant provider access.
+
+The AI User App rows cover the project's
+[User App](../../ai-gateway/user-apps.mdx). **View** lets a user find the User
+App URL, call it with their own personal API keys, and see their own usage and
+allowance. **Edit** covers the User App's policies and per-person budgets.
+**Personal Keys** covers creating and rolling a user's own keys. Users with **AI
+User App** **Edit** can also manage other people's personal keys on the project.
+
+Permissions accumulate. Assigning **AI User** on a project never removes access
+that a user already has from their account role. For example, an account Admin
+who is also a project AI User keeps full access to the project.