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

# Admin Assistant

> Use the in-product Super Admin assistant to inspect platform state and build shareable custom toolkits

The **Admin Assistant** is a chat panel on the Super Admin Dashboard. Use it to inspect platform state and to **build and share custom toolkits** without leaving the admin UI.

In release notes this capability may appear as **Toolkit Management Assistant**. In the product UI the button and panel are labeled **Admin Assistant**.

This is separate from the **Toolkits** tab, which enables and configures built-in enterprise toolkits (OAuth, enable/disable, categories). The assistant works with **custom toolkits** — named bundles of links to Actions and Workflows that already exist in projects.

## Prerequisites

* Your role includes **Custom Toolkits → Manage** (see [RBAC](/super-admin/sa-rbac)). Without it, the **Admin Assistant** button is hidden.
* The Actions or Workflows you want to bundle already exist in a project (the assistant links them; it does not create new tools).
* You know which **team(s)** should receive the shared toolkit.

## Open the panel

1. Open **Super Admin**.
2. In the header bar, click **Admin Assistant** (shield icon).
3. A resizable side panel opens (roughly 400–800px wide; drag the left edge to resize).

| Control      | Purpose                                                         |
| ------------ | --------------------------------------------------------------- |
| **New chat** | Clears the conversation and starts fresh                        |
| **Close**    | Hides the panel (does not change platform state)                |
| Composer     | Placeholder: **Ask the Admin Assistant…** — press Enter to send |
| Stop         | Cancels an in-progress generation when shown                    |

Empty-state copy: **Build and share custom toolkits**, with the note that anything that changes the platform asks you first. Click a suggestion chip to send that prompt.

## What a custom toolkit is

A custom toolkit is a **bundle of links** to things that already exist:

| Linked resource | Where it lives                     |
| --------------- | ---------------------------------- |
| **Actions**     | A project’s Actions library        |
| **Workflows**   | A project’s workflow / Tool Editor |

Important properties:

* The toolkit does **not** copy or own the tool. It points at the original in its home project; edits there apply everywhere the toolkit is shared.
* Once shared with a team, the toolkit is available to agents in that team — there is **no** separate per-agent opt-in step.
* The display **name** is human-readable; the **slug** is immutable and namespaces tool names the model sees.
* The assistant **cannot author** new actions or workflows. Create them in the Actions library or Tool Editor first, then ask the assistant to link them.

## Ask questions vs make changes

| Kind of request | Examples                                                                                                    | What happens                      |
| --------------- | ----------------------------------------------------------------------------------------------------------- | --------------------------------- |
| **Read**        | List teams, list custom toolkits, usage leaderboard, search linkable actions/workflows, get toolkit details | Runs **without** an approval card |
| **Change**      | Create/update/delete toolkit, link/unlink action or workflow, share with teams                              | Shows an **approval card** first  |

### Approval card

When a change is proposed:

1. Review the **tool name**, **risk level**, and **arguments**.
2. Choose **Allow** (or the labeled confirm action) to run it, or **Deny** to leave the platform untouched.
3. Only the **newest** assistant turn holds a live approval — older cards are not replayable.

You do not need to type “please confirm” in chat. Call the change and use the card. The panel subtitle is **Confirms every change before it runs**.

Every tool call is authorized with **your** admin permissions. If a call returns a permission error, the assistant should report what is missing rather than silently trying another route.

## Typical workflow: build and share a toolkit

1. Ask the assistant to create a toolkit (give a clear display name).
2. Point it at the **project(s)** where the Actions or Workflows already live (use project names the assistant can resolve).
3. Have it **search and link** each action or workflow **one at a time**.
4. Ask it to **share** the toolkit with the right team(s).
5. Review the summary: toolkit name, contents, and who can see it.

When linking, the assistant may surface **input warnings** (for example file-upload inputs that may not work for callers outside the tool’s home project). The link can still succeed; treat the warnings as guidance for callers.

### Sharing replaces the team list

Sharing a toolkit with a set of teams **replaces** the full shared-team list. To add one team while keeping others:

1. Read the current shared teams (`get` / inspect the toolkit first).
2. Pass the **existing team IDs plus the new one**.

Passing only the new team would revoke everyone else.

## What the assistant can help with

| Capability                                         | Notes                                                          |
| -------------------------------------------------- | -------------------------------------------------------------- |
| List / inspect custom toolkits                     | Platform-global custom toolkit inventory                       |
| Create, update, delete custom toolkits             | Gated by approval                                              |
| Search linkable actions and workflows in a project | By query within a resolved project                             |
| Link / unlink actions and workflows                | One at a time; watch for input warnings                        |
| Share toolkits with teams                          | Replacement semantics — see above                              |
| List platform teams                                | For sharing and navigation                                     |
| Team usage leaderboard                             | Example: usage over a recent window (for example last 30 days) |
| List projects / project details                    | To resolve where tools live                                    |

It does **not** replace **Super Admin → Toolkits** for enabling built-in toolkits, configuring OAuth, or managing toolkit categories.

## Example prompts

* What custom toolkits exist right now?
* List the teams on this platform.
* What teams have the most usage in the last 30 days?
* Bundle our Jira actions into a toolkit for the Support team.

## Limits and tips

* Never invent IDs in chat — let the assistant resolve teams, projects, actions, workflows, and toolkits from search/list results.
* Prefer precise names when several projects or tools could match; if ambiguous, the assistant should ask which one you meant.
* Use **New chat** when switching to an unrelated task so prior context does not confuse sharing or linking.
* If a tool does not exist yet, create it in the project first, then return to the assistant to link it.
* Built-in toolkit enablement, OAuth, and category controls stay on **Super Admin → Toolkits**.

## Troubleshooting

| Symptom                                         | What to check                                                                             |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------- |
| No **Admin Assistant** button                   | Your role lacks **Custom Toolkits → Manage**                                              |
| Approval card never appears but nothing changes | You may have **Denied**; or the request was read-only                                     |
| Permission error mid-flow                       | Your role can open the assistant but lacks a specific admin API permission the tool needs |
| Sharing dropped other teams                     | Sharing is a full replace — re-share with the complete team list                          |
| Cannot find an action/workflow                  | Wrong project, or the tool was never created in that project                              |
| Input warnings after link                       | Review warnings; link may still be valid for some callers but not others                  |

## Related

* [RBAC](/super-admin/sa-rbac) — Custom Toolkits Manage permission and Toolkits tab access
* [Teams](/super-admin/sa-teams) — team structure the assistant can list and share with
* [Agent toolkits overview](/agents/toolkits/overview) — toolkits on agents (distinct from this admin assistant)