# Install and Manage Team Plugins

> Install, update, and uninstall team plugins from Marketplace or local packages

Source: https://doc.fastgpt.io/plugin/team-installation
Last Updated: 2026-11-12

> Team plugins require a FastGPT Commercial Edition license and must be enabled by a system administrator under **Admin → System Config → Feature Flags → Allow teams to upload plugins** (disabled by default and unavailable in the open-source Community Edition).

Team plugins are installed and managed by team administrators or owners and are available only within the current team. Team members can use installed plugins in workflows, Agents, and tool selectors.

## Scope

Team plugins and system plugins are independent installations:

* System administrators install and configure system plugins for use across teams.
* Team administrators install team plugins for the current team.
* The same plugin can exist as both a system plugin and a team plugin. Both entries are displayed, and the system entry carries a **System** label.
* A team plugin does not inherit secrets, pricing, status, version, or other configuration from a system plugin with the same ID.
* Teams cannot hide or change the visibility of system plugins.

Team plugins can be updated or uninstalled and do not have a deprecation state.

## Roles

* **System administrator**: A user signed in with the `root` account, with the **Admin** entry at the bottom-left of the sidebar, responsible for system-wide configuration and system plugins.
* **Team owner**: The creator of the current team, holding full administrative permissions within the team by default.
* **Team administrator**: A team member granted the **Admin** permission under **Account → Team → Permissions**.

## Prerequisites

Before installing a plugin, confirm that:

1. Your account is a team administrator or team owner. Regular members can use installed plugins but cannot install, update, or uninstall them.
2. The system administrator has enabled **Allow teams to upload plugins** under **Admin → System Config → Feature Flags**. This toggle gates all team plugin installation methods; Marketplace installation, local uploads, and installation confirmation are rejected when it is disabled.
3. The deployment can access FastGPT Marketplace when installing from Marketplace.
4. For a local installation, you have a valid `.pkg` file or a `.zip` archive containing one or more `.pkg` files.

The **New Tool** button in the upper-right corner is visible only when your account is a team administrator or owner and **Allow teams to upload plugins** is enabled. When the deployment disables the Marketplace (`disableMarketplace`), the menu shows only **Install from Local**.

Authors preparing a custom package can follow [debugging, packing, and publishing](https://doc.fastgpt.io/plugin/debugging-and-publishing#build-check-pack). System administrators can follow [system tool management](https://doc.fastgpt.io/guide/build/tools/system-plugins/upload_system_tool) for system-wide installation.

## Install from Marketplace

1. Open **Studio → System Tools**.
2. Click **New Tool** in the upper-right corner and select **Install from Marketplace**.
3. Find a plugin by name, source, or category. You can enable the **Only show uninstalled** filter.
4. Open the plugin details and review its description and version information.
5. Select a version and click **Install** to continue.

![Team plugin Marketplace and tool installation entry](https://cdn.jsdelivr.net/gh/labring/fastgpt-img@main/optimized/current/team-plugin-marketplace.png.webp)

After installation, the plugin appears in the team tool list and can be selected in workflows and Agents. Configure any required secrets or runtime parameters before use.

## Upload a Local Package

When team plugin uploads are enabled, you can install plugins you developed yourself or obtained through other channels:

1. Open **Studio → System Tools**.
2. Click **New Tool** and select **Install from Local**.
3. In the **Import/update Plugin** dialog, select one or more `.pkg` files, or a `.zip` archive containing multiple `.pkg` files.
4. Wait for FastGPT to upload and inspect the packages.
5. Review the **Name, Tag, Intro, Status, and Action** columns in the parsed list. Failed files display an individual error and can be removed or retried.
6. Click **Confirm import**.

Uploading and parsing only prepare an installation preview. The plugin is installed for the team after confirmation.

## Update a Plugin

When Marketplace provides a newer version, an update option appears on the plugin card or details page:

1. Open the team Marketplace and locate the plugin.
2. Review the release notes and permission changes.
3. Select the target version and update the plugin.
4. Test workflows and Agents that use the plugin.

For local packages, upload the target version again and confirm the installation. Team configuration remains independent from the system installation.

Plugin updates may change input and output schemas, secret requirements, or runtime behavior. Validate updates in a test application before updating production workflows.

## Uninstall a Plugin

A team administrator can click **Uninstall** from the tool card menu or details drawer, then enter the plugin name in the **Confirm uninstalling this team plugin?** dialog.

Uninstalling:

1. Deletes the installation under the current team source from the plugin service.
2. Revokes future runtime access for the current team.
3. Removes the team plugin from new tool selection flows.

Existing workflow and Agent nodes are not rewritten. They fail on their next run after the plugin is uninstalled. Reinstall the plugin from Marketplace or upload its package again to restore access.

Uninstalling a team plugin does not affect a system plugin with the same ID or installations owned by other teams.

## System and Team Copies

When the same plugin is installed at both levels:

* The team entry appears before the system entry.
* The system entry displays a **System** label next to its title. Hover over the label to read its explanation.
* Workflows and Agents store the plugin source, so each copy can be selected and configured independently.
* Uninstalling the team copy leaves the system copy available.

Use clear internal conventions when both copies exist, especially when they have different versions or configuration.

## Security Recommendations

* Install packages only from trusted sources and review plugin descriptions and secret requirements.
* Apply your team's data security policy when a plugin accesses external URLs, accounts, or secrets.
* Review release notes and test compatibility before upgrading.
* Check workflow and Agent references before uninstalling a plugin.
* For troubleshooting team plugin installation, permissions, and secret isolation, see [App, Chat, and Plugin FAQ](https://doc.fastgpt.io/guide/build/faq#team-plugin-installation-and-management).
