Skip to main content

Managing Copilot Installation in an Application

Learn how to deploy Copilots to applications and manage their availability, access permissions, and enabled status in Yeeflow.

Updated today

This article explains how administrators deploy (install) Copilots to an application and manage their availability and access permissions in Yeeflow.

Copilot Installation controls:

  • Which application a Copilot is deployed to

  • Who can access the Copilot

  • Whether the Copilot is enabled in the application

It does not configure the Copilot’s capabilities (Instructions, Knowledge, or Tools).


Where to Manage Copilot Installation

Copilot Installation is an application-level setting.

Navigation Path

  1. Open the target application

  2. Go to Application Settings

  3. Expand AI agent

  4. Click Copilot installation

You will see the Deployed Copilot list for the current application.

【📸 Screenshot: Application Settings → AI agent → Copilot installation】


Understanding the Deployed Copilot List

The Deployed Copilot list shows all Copilots deployed to the current application.

Each Copilot includes the following information:

  • Copilot – Copilot name and icon

  • Deployed by – Administrator who deployed the Copilot

  • Deployed time – Deployment time

  • Access by – Who can access the Copilot

  • Enabled – Whether the Copilot is currently enabled

This page is the central place to manage Copilot availability and access.


Deploying (Installing) a Copilot to an Application

Clicking Install Copilot opens the Deploy Copilot to application dialog, where you configure the deployment.


Deploy Copilot to Application Dialog

The dialog includes the following options:

1. Choose application

Select the application where the Copilot will be deployed.

  • The current application is selected by default

  • If you have permission, you may choose another application

2. Choose Copilot

Select a Copilot from the list of Published Copilots.

  • Copilots created in the current application

  • Copilots from other applications

3. Who can access this Copilot?

Define who can use the Copilot in the application:

  • All Users

    • All users in the application can access the Copilot

  • Specified Users

    • Only selected users or user groups can access the Copilot

This setting determines the Copilot’s visibility and access scope.

4. Deploy

Click Deploy to complete the installation.

After deployment:

  • The Copilot appears in the Deployed Copilot list

  • If Enabled is turned on, it is immediately available to authorized users


Managing Access Permissions (Access by)

After deployment, administrators can update Copilot access permissions at any time.

To edit access permissions:

  1. Locate the Copilot in the Deployed Copilot list

  2. Click the action menu (⋯)

  3. Update the Access by setting

  4. Save the changes

Permission changes take effect immediately—no redeployment is required.


Enabling or Disabling a Copilot

The Enabled toggle controls whether the Copilot is active in the application.

  • Enabled = On

    The Copilot is visible and usable by authorized users

  • Enabled = Off

    The Copilot is temporarily unavailable but remains deployed

This is useful for temporarily disabling a Copilot without removing it.


Removing a Copilot from an Application

If a Copilot is no longer needed in the current application, it can be removed.

Notes on removal:

  • Removal affects only the current application

  • The Copilot itself is not deleted

  • Deployments in other applications are not affected

To remove a Copilot:

  1. Find the Copilot in the Deployed Copilot list

  2. Click the action menu (⋯)

  3. Select Delete

  4. Confirm the action


Copilot Installation vs. Copilot Configuration

It is important to distinguish between these two concepts:

  • Copilot Configuration

    • Managed in Copilot Management

    • Defines what the Copilot can do (Instructions, Knowledge, Tools)

  • Copilot Installation

    • Managed in Application Settings

    • Defines where the Copilot is available and who can access it

Installation does not change Copilot behavior—only its application-level availability.

Did this answer your question?