> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.
# App Management
[Back to Admin Console Guide](/ai-for-service/administration/overview)
The App Management module lets admins deploy, approve, and assign apps developed on the Platform. From here you can approve or reject deployment requests, manage tasks, and assign bots to users or groups.
***
## Deploying Bots
After a developer publishes a bot from Bot Builder, it appears on the **Deployment Requests** page. Bots are not available to users until the admin approves and assigns them.
### Approval Modes
| Mode | Behavior |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Auto-approve** | Bots are approved immediately when published and skip the Deployment Requests page. Configured under [Preferences](#preferences). |
| **Manual approval** | Admin must review and approve each request before the bot is available to users. |
### Deployment Request Columns
| Column | Description |
| ------------ | ------------------------------------------------- |
| Bot Icon | Icon displayed to end-users |
| Bot Name | Name of the bot |
| Bot Type | Standard, Universal, etc. |
| Tasks | Number of tasks in the bot |
| Version | New (never deployed) or Upgrade (updated version) |
| Purpose | Consumer Use or Enterprise Use |
| Requested by | Developer who submitted the bot |
| Requested on | Submission date |
### To Approve a Bot
1. On the **Deployment Requests** page, hover over the bot and select the **Publish** icon.
2. Optionally, select **Bot** to review pending tasks and details (dialog tasks, NL config, channels, API extensions, settings, comments).
3. Select **Next** (or **Publish** for upgrades).
4. On approval success, select **Continue** — you are redirected to the Enterprise or Consumer Bots page based on the deployment model.
### To Reject a Bot
1. On the **Deployment Requests** page, hover over the bot and select the **Reject** icon.
2. In the **Reject bot** dialog, select the tasks to reject.
3. Enter a reason in the **Provide a reason** field.
4. Select **Reject**.
The bot is removed from the Deployment Requests page and its status reverts to *Configured* in Bot Builder.
***
## Managing Enterprise Bots
Enterprise bots are approved bots with the deployment model set to **Enterprise**. They must be assigned to users before anyone can access them.
### Columns
| Column | Description |
| ------------ | ----------------------------------- |
| Bot Name | Name of the bot |
| Published By | Developer who published the bot |
| Bot Type | Standard, Universal, etc. |
| Channels | Channels the bot is accessible from |
### Assigning Users
1. Select the **Ellipses** icon for the bot and choose **Bot & Task Assignments**.
2. Select **Assign Bot's Tasks** (or **No assignments** to disable access for all users).
3. Expand a task and choose one of:
* **All users in your enterprise** — All current and future users
* **Assign user groups** — Opens a group selector dialog
* **Assign individual users** — Opens a user selector dialog
4. Select **Done** → **Done** → **Apply**.
### Bot Settings
From the **Ellipses** icon, select **Bot Settings** to:
| Setting | Description |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Auto Approve** | Do not approve, auto-approve all, or auto-approve specific components (New Channels, New Tasks, Channel Upgrades, Task Upgrades) |
| **Deployment model** | Read-only — shows Enterprise use |
| **Approved channels** | Select or clear channels available to users (at least one must be enabled) |
| **Notify users** | Send email notifications for bot changes |
| **Email developer** | Open mail client to email the bot developer |
Select **Apply** to save.
### Change Bot Owner
1. Assign a new role to the current owner.
2. Select the new owner from the list of developers.
### Managing Bot Tasks
After deployment, you can suspend or reactivate individual tasks.
**About suspended tasks:** Users can't access suspended tasks. The bot doesn't send alerts or respond to action requests for suspended tasks. An alert is sent to configured users when a task is suspended or reactivated. Developers can still update suspended tasks in Bot Builder — they remain suspended until the admin reactivates them.
1. Select **Ellipses** > **Manage Bot tasks**.
2. Expand the **Bot tasks** field.
3. Select or clear task checkboxes to deploy or suspend.
4. Select **Confirm** twice.
***
## Managing Consumer Bots
Consumer bots are approved bots with the deployment model set to **Consumer**. They are available to customers immediately after approval — no user assignment is needed.
### Additional Columns
| Column | Description |
| --------- | -------------------------------------- |
| Plan Type | Plan under which the bot was published |
### Bot Settings, Change Owner, and Manage Tasks
Same process as Enterprise Bots — see sections above. Bot Settings for consumer bots omits the user notification option.
### Restore a Bot
A published bot with active dialog tasks can be restored within 30 days of deletion.
1. On the **Consumer Bots** page, select **Ellipses** > **Restore** for the bot.
Restoration reinstates the app with all pre-deletion configurations.
***
## Managing Smart Bots
Smart bots are displayed on the **Smart Bots** page. Management follows the same pattern as Enterprise and Consumer bots.
### Columns
| Column | Description |
| ------------ | ------------------------------------ |
| Bot Name | Name of the bot |
| Published by | Developer who created the bot |
| Tasks | Number of tasks |
| Channels | Channels where the bot is accessible |
***
## Preferences
The Preferences page controls the admin approval process at the account level. You can automate deployment approvals and bot task assignments.
### Automate Deployment Requests
1. Under **Deployment Requests**, select **Automatically approve all new deployment requests**.
2. Select **Save**.
### Automate Bot Assignments
Bot assignments cannot be automated unless deployment requests are already set to auto-approve.
1. Under **Enterprise Bots Assignments**, select **Automatically assign all approved bots, their tasks, and channels**.
2. Select **Save**.
When both are automated, users receive new bots immediately after a developer publishes them.
### Manual Approval
1. Under **Enterprise Bots Assignments**, select **Hold all deployment requests for manual admin approval**.
2. Select **Save**.
***
## Deleted Bots
Permanently deleted bots are listed on the **Deleted Bots** page.
| Column | Description |
| --------------------- | ------------------------------- |
| Bot Name | Name of the deleted bot |
| Deletion requested by | User who requested deletion |
| Deletion Request | Date the deletion was requested |
| App Creation Date | Date the app was created |
| Deletion Date | Date of permanent deletion |