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

# Kits Management

> Manage reusable kits for your organization.

<style
  dangerouslySetInnerHTML={{ __html: `
/* qwenwork-navigation-tabs-override */
#adoc-layout { --topbar-height: var(--topbar-row1-height) !important; }
#navbar[data-has-tabs="true"] > div:has(.nav-tabs) { display: none !important; }
` }}
/>

## 1. What you can do

A kit combines multiple professional capabilities into a solution for a role or business scenario. Admins can:

- control whether members can browse the public kit marketplace or submit kits to the organization;
- create and maintain organization-owned kits;
- control whether an organization kit is visible to members; and
- review kits submitted by members.

## 2. Configure kit access

The top of the page contains three organization-wide settings.

### Public marketplace visibility

- On: Members can browse the public kit marketplace.
- Off: The public marketplace entry is hidden. Public kits that are already installed are not automatically removed.

### Allow personal kit uploads

This capability is marked **Coming soon** and cannot currently be changed.

### Allow members to add kits to Organization kits

- On: Members can submit kits to the organization. New submissions appear under **Kit reviews**.
- Off: Members cannot create new organization submissions. Existing review records remain available.

## 3. Create an organization kit

1. Open **Organization kits**.
2. Select **Create kit**.
3. Enter the kit information.
4. Upload an icon and kit ZIP package when needed.
5. Set the supported clients and team visibility.
6. Select **Create**.

### Field reference

| Field                | Required | Guidance                                                                    |
| -------------------- | -------- | --------------------------------------------------------------------------- |
| Kit name             | Yes      | Unique technical identifier in the organization, for example `sales-expert` |
| Display name         | No       | English or general display name                                             |
| Chinese display name | No       | Name shown in the Chinese interface                                         |
| Summary              | No       | Explain the business scenario addressed by the kit                          |
| Version              | No       | Use a clear version such as `1.0.0`                                         |
| Icon                 | No       | Image file up to 2 MB                                                       |
| Supported clients    | Yes      | Choose where members can discover the kit                                   |
| Team visibility      | No       | When on, the kit is shown in the team's marketplace                         |
| Kit ZIP package      | No       | ZIP only, up to 50 MB                                                       |

The kit name cannot be changed after creation. To use a different technical identifier, create a new kit.

## 4. Prepare a kit package

A kit package can include:

- `README.md` for documentation;
- `README_EN.md` for English documentation;
- skill files used by the kit; and
- other configuration files required by the kit.

After upload, the page attempts to read documentation from the package. If it reports that no README was found, the kit can still be saved, but members may not see complete usage instructions.

Before uploading, verify that:

- the ZIP file is no larger than 50 MB;
- the README explains the intended scenario, required input, and limitations;
- all skills and configuration files come from trusted sources; and
- the package contains no real passwords, access tokens, personal information, or customer data.

When editing, the existing package is retained if no new file is selected.

## 5. Find and review kits

1. Search by name under **Organization kits**.
2. Review the kit name, summary, composition, version, supported clients, status, and update time.
3. Use pagination to view more kits.

The **Composition** column shows the number of skills and connectors included in the kit, helping admins understand its complexity.

## 6. Edit a kit

1. Find the kit.
2. Select **Edit**.
3. Change the display name, Chinese display name, summary, version, icon, supported clients, or team visibility.
4. To update the content, choose a new ZIP file.
5. Select **Save changes**.

Download and retain the previous package before an update, and use the version field to record changes.

## 7. Control team visibility

Use **Team visible** in the list:

- On: The kit appears in the team's marketplace.
- Off: The kit is hidden from the team's marketplace. Members who already installed it are not affected.

For a kit still being tested, keep team visibility off until validation is complete.

## 8. Download or remove a kit

### Download a package

1. Find the kit.
2. Select **Download**.
3. Save the ZIP file for backup or review.

### Remove a kit

1. Select **Remove** for the kit.
2. Verify the kit name.
3. Confirm removal.

The Admin console does not currently provide a restore action. Download and retain required files before removal.

## 9. Review member submissions

1. Open **Kit reviews**.
2. Filter by **Pending**, **Approved**, **Rejected**, **Cancelled**, or **All**.
3. Select **Details** and review the name, summary, author, version, supported clients, and package.
4. For a pending submission:
   - select **Approve** to publish it to Organization kits; or
   - select **Reject**, enter a reason, and return it to the submitter.
5. Confirm that the submission status has updated.

When reviewing a kit, also confirm that all included skills and connectors comply with the organization's security and authorization requirements.

## 10. Troubleshooting

### Package upload fails

Confirm that the file is a ZIP under 50 MB, remove unnecessary large files, and try again.

### The page reports that no README was found

Add `README.md` or `README_EN.md` to the ZIP with the kit purpose and instructions, then upload it again.

### The kit exists but members cannot see it

Check team visibility, supported clients, and the member's current organization workspace.

### Why is personal upload unavailable?

Personal kit uploads are not currently available. Submitting a kit to the organization uses the separate **Add to organization** setting.

---

[Previous: Skills](/enterprise/skills) · [Back to overview](/enterprise/admin-overview) · [Next: Connectors](/enterprise/connectors)