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

# Attach resources

> How to attach skills, connectors, and knowledge to an agent

An agent's capability is defined by the resources attached to it: skills, connectors, and knowledge. Resources live in one of two places.

| Location             | Description                                                                                                                  |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Workspace shared** | Shared resources managed under "Configure" in the sidebar (Skills / Knowledge / Connectors). Multiple agents can attach them |
| **Agent-specific**   | Resources used by one agent only. Registered from the agent detail page; they do not appear on the shared pages              |

## Attaching skills

Open the **Skills** section of the agent's configuration panel (the gear icon in the detail page's header) and click "Add skill."

* Search for a workspace-shared skill and attach it, or use "Create new" to build an agent-specific skill from scratch
* There is a limit on how many skills can be attached to one agent (the remaining count is shown on the add screen)
* To use a shared skill with small tweaks, use "**Copy to this agent and edit**" (fork)

<Warning>
  Editing a workspace-shared skill **affects every other agent** it is attached to. Be mindful of the blast radius.
</Warning>

## Attaching connectors

Manage these in the **Flow** and **Connectors** sections of the configuration panel.

* **jinba-flow** — Jinba connections are grouped into "**In use**," "**Available · Connected in workspace**," and "**Available · Not connected (connect to use)**." Press "**Connect**" to attach one in one click. Your own workspaces also appear in the not-connected group and connect as connections dedicated to this agent (marked with an "**Agent-only**" badge)
* **Add connector** (Custom MCP) — pick a shared MCP connection, or register an agent-specific MCP server

Agent-specific connections do not appear to other agents or in the workspace catalog. Use them for connections you want to keep scoped, such as department-specific systems.

The panel also shows an "**External services (personal)**" group listing the personal services you have connected — Gmail, Slack, and the rest — each with a "**Connected**" badge. This is a status view, not something you attach: personal connections are yours, active in all of your chats in this workspace whichever agent you use, and are managed on the [Connectors page](/en/pages/jinba_app_neo/connectors/personal-connectors) (the group links there). With nothing connected it reads "**No connected external services yet.**"

### Choosing which flows the agent uses

An attached Jinba Flow workspace exposes **all** of its published flows to the agent by default. To narrow that, open the workspace in the Flow connectors section and switch its flow list from "**Use all**" to "**Only selected**."

* The flow table becomes a checklist: tick the flows this agent may use, filter them by name, or narrow the view to "**Selected only**." Selected flows sort to the top, and a counter shows how many are ticked
* Nothing changes until you press "**Save**" — "**Revert**" discards the edits, and a note reminds you the change "**Takes effect from the next chat once saved**"
* Saving with nothing ticked is allowed, but the table warns you first: "**Nothing is selected. The AI will not see any flow from this workspace.**"
* Flows that have not been synced yet show "**Selectable after the next sync**" — refresh the connection to make them selectable. While "Only selected" is active, flows published later are **not** added automatically; tick them when you want the agent to use them
* The selection is **per agent, per connection**: the same connected workspace can expose a handful of flows to one agent and everything to another. Switching back to "Use all" restores the default

In that agent's chats, the composer follows the selection — the `#` picker and the "+" menu's Flow list offer only the selected flows ([Composing messages](/en/pages/jinba_app_neo/chat/composer)). If the AI is asked to run an excluded flow, it explains the flow is excluded and that it can be added from the agent's Flow settings.

## Attaching knowledge

Open the **Knowledge** section of the configuration panel and click "Add knowledge."

* **Attach files individually; sync folders wholesale** — setting a folder to "auto-sync" means files added to the folder later are automatically reflected in the agent
* Search and select workspace files and folders, or drag and drop files right there to add them (pasting URLs is supported too) — files and URLs added this way become agent-specific material
* "**Import from Notion**" at the bottom of the picker registers Notion pages as agent-specific knowledge. It opens the "**Add Knowledge (this agent only)**" dialog, where you paste the page URL and choose a destination folder

The Knowledge section shows each item's sync status, size, and how many agents use it — the same information as the workspace Knowledge page. Agent-specific folders offer the full folder menu (add source, create subfolder, rename, move, delete) and drag-and-drop moves within the agent's scope; folders mirrored from the workspace stay read-only, and auto-synced folders offer "**Stop syncing**" only.

<Note>
  There is a limit on how many knowledge sources are loaded automatically when a chat starts. Sources beyond the limit are not auto-loaded, but the AI can still search for and retrieve them as needed. See [Organize knowledge](/en/pages/jinba_app_neo/knowledge/organize) for details.
</Note>

## Detaching

Remove attachments from the list in each section. In the Knowledge section, the action depends on where the item lives: a workspace-shared item shows "**Remove from agent**" — the source itself stays in the workspace and can be re-added later — while an agent-specific item shows a red "**Delete**" with a confirmation, and deleted agent-specific resources cannot be restored. Bulk selection adapts the same way ("Remove from agent" / "Delete selected"; a mixed selection shows "**Delete / remove**" with a single confirmation covering both).