--- title: Manage capabilities and connections description: Add apps and skills on the Apps page, and configure connections, extensions, and the environment. lastVerified: 2026-10-22 --- # 3.10 Manage capabilities and connections Manage installed skills and connections under **Marketplace > My apps and skills**. The marketplace **Apps** and **Skills** categories discover resources to add; the management page shows installation, connection and availability status. ## Add and configure resources 1. Open **Marketplace**, choose **Apps** or **Skills**, and find a resource through search or use-case categories. 2. Select **Add** or **Install**; open the entry to inspect its source and permissions. To bring your own content, choose **Create** and the relevant creation or import entry. 3. Check the status (for example Added, Not connected, Awaiting authorization, or Installed). For an app that needs an account, select **Set up connection** to finish configuration. 4. Give each employee who will use it its own permission, then test it once. Connecting an account does not give employees access. “Added” only means the resource is now managed by Teloa. It does not prove that a connection works or a tool is authorized. [![My apps and skills manages installed methods and connections. Built-in skills are shown here.](https://docs.teloa.ai/v/0.2.6/assets/screenshots/en/capabilities-024.f287a91cd6cf.png)](https://docs.teloa.ai/v/0.2.6/assets/screenshots/en/capabilities-024.f287a91cd6cf.png) *0.2.4 actual interface with example data. My apps and skills manages installed methods and connections. Built-in skills are shown here.* ## Connect external tools Set up app connections with **Set up connection** on **Apps**; configure MCP and native capabilities in **Settings > Connections and environment**. Data sources, business associations, and employee permissions have their own configuration pages. Test read access first, then enable only the write capabilities you need. ### Connect your own MCP Server 1. Choose **Create app** in app management. Describe its name, purpose, MCP URL and authentication method. Do not include secret values. 2. Generate the connection draft in the original conversation. Review its URL and authentication Header definitions, then open the authentication card. 3. Enter authentication values yourself in the dedicated controls and choose **Add and connect**. Streamable HTTP is supported. Remote URLs use HTTPS; local loopback URLs may use HTTP. Static authentication supports up to eight Headers, each with a name and optional prefix. 4. Inspect the tools actually discovered by the connection, then authorize the employees who need them. Remote read-only hints do not grant employee permissions. 5. Retry failures on the same connection. Changes to the URL or definition require authentication to be confirmed again. Rotate keys, disconnect or delete the connection as needed. Keep credentials out of chat and templates. This connects employees to external tools. For external systems calling Teloa employees, see [Employee API, SDK and MCP](https://docs.teloa.ai/v/0.2.6/markdown/en/develop/employee-api.md). Connections may show “Read,” “Write,” or “Write · Needs your approval.” These labels provide guidance. They do not replace checking the specific tool, its parameters, and its execution boundaries. ## Settings navigation Settings are grouped by purpose: **Preferences** (General settings), **Models and services**, **Capabilities and connections** (Execution locations, Connections and environment, IM channels, and more), **Working style** (Auto Dream, Agent presets), **Advanced** (including Component status), and **About**. Component status opens directly. ## Manage extensions and the environment 1. Native extension details separate installation source, enablement, and actual running state. Enabled does not mean successfully running. 2. Apps from a business show their actual installation status. Follow the prompts when installation is needed. If the status cannot be confirmed, it shows “Not verified”; refresh to check again. **View settings** opens the resource. Registration alone does not mean it is installed or needs a restart. 3. **Settings > Connections and environment**, labeled “Everyday configuration and management”, lets you manage run configuration and native extensions directly. Open Terminal, Agent Loop, Subagent, or Web Search to edit and save settings without leaving this page. You can also install, enable, disable, or remove extensions here. 4. **Settings > Component status** is for inspecting components and troubleshooting problems while it runs. It provides a read-only inventory of global and session-preset components. **IM channels** is built into the app, so you do not install or enable it from the marketplace. Add and enable each channel under **Settings > IM channels**; see [IM channels](https://docs.teloa.ai/v/0.2.6/markdown/en/guides/im-channels.md). Install and manage other native extensions in Settings. Handle pending older installations under **Apps > App installation records** first. Browser and Computer are off by default; Auto review is loaded on first start but does not change a conversation's default permissions. Enabling an extension does not grant employee permissions. Available capabilities depend on the run preset and configuration. See [Native execution capabilities](https://docs.teloa.ai/v/0.2.6/markdown/en/guides/native-capabilities.md) for operational boundaries. ## Web search and reading policy In **Settings > Connections and environment**, expand **Web search and reading policy**. After you turn it off and save, conversations and tasks cannot start new web searches or page reads. Existing employee grants are kept. This does not cancel requests already sent or control network access through Browser Use, Computer Use, terminal commands, or MCP. The website list only restricts domains and subdomains directly requested by the page-reading tool. It does not filter search results or check redirect destinations against that list. Search service parameters remain in the native Web Search configuration; each employee’s tool access remains in employee authorization. Developers can start with [skills](https://docs.teloa.ai/v/0.2.6/markdown/en/develop/skills.md), [resource packages](https://docs.teloa.ai/v/0.2.6/markdown/en/develop/packages.md), and [read-only MCP](https://docs.teloa.ai/v/0.2.6/markdown/en/develop/mcp.md). Actual extension availability still depends on matching dependencies needed to run it, configuration and authorization. Develop your own [apps](https://docs.teloa.ai/v/0.2.6/markdown/en/develop/apps.md) or [SKILLs](https://docs.teloa.ai/v/0.2.6/markdown/en/develop/skills.md); see [Sharing and receiving](https://docs.teloa.ai/v/0.2.6/markdown/en/guides/sharing.md) for exports, public links, recipient setup and revocation.