zuplo 7.9.4 → 7.9.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "7.9.4",
+  "version": "7.9.6",
   "type": "module",
   "description": "The official Zuplo CLI for local development and platform management",
   "homepage": "https://zuplo.com/docs/cli/overview",
@@ -32,9 +32,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "7.9.4",
-    "@zuplo/core": "7.9.4",
-    "@zuplo/runtime": "7.9.4",
-    "@zuplo/test": "7.9.4"
+    "@zuplo/cli": "7.9.6",
+    "@zuplo/core": "7.9.6",
+    "@zuplo/runtime": "7.9.6",
+    "@zuplo/test": "7.9.6"
   }
 }

package/docs/ai-gateway/managing-teams.mdx

@@ -1,87 +0,0 @@
----
-title: Managing Teams
-description:
-  Create teams and sub-teams, add members, and set team-level policy templates
-  and usage limits in your AI Gateway project.
----
-
-Teams in the Zuplo AI Gateway grant users access to apps. Teams are
-hierarchical, so access propagates to sub-teams only when the user also has
-permission to view the Zuplo project that contains the AI Gateway. Team or
-sub-team membership doesn't grant Zuplo project access. Teams are also where you
-define usage limits and [policy templates](./policy-templates.mdx).
-
-## Creating a Team
-
-Creating a team requires Admin rights on the Zuplo project or Zuplo account for
-a top-level team, or on the parent team for a sub-team. As a convenience, the
-Portal disables the **New Team** button when you don't have the required rights.
-
-<Stepper>
-
-1. Open the [Apps & Teams](https://portal.zuplo.com/+/account/project/ai/teams)
-   tab of your AI Gateway project in the Zuplo Portal.
-
-1. Click **New Team** above the tree.
-
-1. Choose where the team sits. Once the gateway has at least one team, the
-   dialog shows a parent picker above the name field; leave it on **No parent
-   team** for a top-level team, or pick a team to create a sub-team under it.
-
-1. Enter the name of your team.
-
-1. Click **Create Team**
-
-</Stepper>
-
-You can also create a sub-team from the parent itself: select it in the tree and
-click **Create Sub-Team** in the team's header.
-
-After creating a team, use its tabs to configure it:
-
-- **Policy Template**—the team's [policy template](./policy-templates.mdx), the
-  starting policy chain for apps created in the team.
-- **Usage & Limits**—shared budgets for the team, its sub-teams, and their apps.
-  See [Usage Limits](./usage-limits.mdx).
-- **Members**—who belongs to the team.
-
-## Adding Team Members
-
-Team members are the users who belong to a team and can access its apps,
-provided they also have permission to view the Zuplo project. AI provider access
-is separate and depends on the user's Zuplo account or Zuplo project role.
-
-<Stepper>
-
-1. Open the [Apps & Teams](https://portal.zuplo.com/+/account/project/ai/teams)
-   tab of your AI Gateway project in the Zuplo Portal.
-
-1. Select the team you want to add members to.
-
-1. Click the **Members** tab.
-
-1. Click **Add Member**.
-
-1. Type the email address of the user you want to add. If the user is already a
-   member of your Zuplo account, they are added directly to the team. Otherwise,
-   they are invited to join the Zuplo account and then added to the team.
-
-1. Select the role for the user:
-   - **Member**: Can access apps owned by the team.
-   - **Admin**: Can manage the team's settings, members, and apps.
-
-     :::caution{title="The Member role requires RBAC"}
-
-     Role-based access control (RBAC) is an optional enterprise add-on on your
-     Zuplo account. Without it, every invited user is an **Admin**. For more
-     information see the
-     [document on roles and permissions](../articles/accounts/roles-and-permissions.mdx).
-
-     :::
-
-1. Click **Add Member** to confirm.
-
-1. The user will receive an email notification if they're being invited to the
-   Zuplo account.
-
-</Stepper>

package/docs/ai-gateway/teams.mdx

@@ -1,49 +0,0 @@
----
-title: AI Gateway Teams
-sidebar_label: Overview
-description:
-  Teams manage access to AI Gateway apps, carry usage limits and policy
-  templates, and organize members with hierarchical sub-teams.
----
-
-Teams are used to manage access to AI Gateway apps, set usage limits, and
-monitor activity. Each team can have multiple members and sub-teams. Use teams
-to group users by department, initiative, or any other logical grouping.
-
-## Teams & Apps
-
-Every [app](./apps.mdx)—each service or integration that calls the AI
-Gateway—belongs to exactly one team. What a team member may do to an app depends
-on that member's role.
-
-Teams also carry a [policy template](./policy-templates.mdx)—the policy chain
-that apps created in the team start with—and [usage limits](./usage-limits.mdx)
-that apply to the team's own usage and all descendant sub-teams and apps.
-
-## Members
-
-Members are the users who belong to a team. Their permissions combine their role
-in the Zuplo account, the Zuplo project that contains the AI Gateway, and the
-team.
-
-There are two roles at the team level:
-
-- **Member**: Can access apps owned by the team.
-- **Admin**: Can manage the team's settings, members, and apps.
-
-Team roles don't grant access to AI providers. Providers are configured for the
-Zuplo project, and access to view or manage them depends on the user's Zuplo
-account or Zuplo project role. A user also needs permission to view that project
-before their team role grants access to the team's apps.
-
-For more information on roles and permissions, see the
-[document on roles and permissions](../articles/accounts/roles-and-permissions.mdx).
-
-**Additional Resources**
-
-- [Role Permissions](../articles/accounts/roles-and-permissions.mdx) - Details
-  on Zuplo account, Zuplo project, and AI Gateway team roles.
-- [Creating & Editing Teams](./managing-teams.mdx) - How to create and edit
-  teams.
-- [Creating & Editing Apps](./managing-apps.mdx) - How to create, configure, and
-  delete apps.