> ## Documentation Index > Fetch the complete documentation index at: https://docs.vybe.build/llms.txt > Use this file to discover all available pages before exploring further. # Capabilities > Choose a coworker's model, which tools it can use, and how much access it gets to each one Capabilities control what an AI coworker is allowed to do: search the web, work with documents, query databases, post in Slack, and more. Turn off what a coworker doesn't need, or limit it to reading, so it only acts the way you intend. Open a coworker's **Overview** and select the **Capabilities** tab. The coworker's owner, and people with **Can edit** or Admin access to it, can change these settings. Everyone else sees "You have read-only access to these settings." ## Automatic model selection **Automatic model selection** ("Automatically pick the best model for the task.") is on by default. Vybe then picks a suitable model for each conversation. Turn it off to choose yourself. A model picker appears below the switch: pick a tier (**Cheap**, **Balanced** or **Smart**) or a specific model. This is the same setting as the model pill in the coworker's chat, and it applies to the coworker for everyone. See [Choose a model](https://docs.vybe.build/coworkers/chatting.md#choose-a-model) and [AI models](https://docs.vybe.build/reference/ai-models.md). Below it, **AGENTS.md** has an **Edit AGENTS.md** button. See [Instructions](https://docs.vybe.build/coworkers/instructions.md). ## Capability settings Each capability is a row showing its current access and a switch. Turning the switch on gives **Full access**; turning it off sets it to **Off**. For finer control, click the row to open its permissions page and choose an **Access level**: | Access level | What the coworker can do | | - | - | | **Full access** | Everything the capability covers | | **Read only** | Only actions that read. Anything that sends, creates, edits or deletes is blocked. | | **Custom** | Only the actions you switch on, listed under **Read-only** and **Write / Delete**. The row then shows **Limited** and how many actions are allowed. | | **Off** | Nothing. The coworker can't use the capability. | **Read only** is only offered for capabilities that have actions that change things, and **Custom** only for capabilities with more than one action. | Capability | What it lets the coworker do | Access levels | | - | - | - | | **External Databases** | Run SQL queries against external databases connected to your organization | Full access, Off | | **Files** | Parse documents like PDFs and spreadsheets, extract data from them, split them and edit them. Turning it off also hides **Knowledge → Files**. | Full access, Read only, Custom, Off | | **Image Generation** | Generate images from text prompts | Full access, Off | | **Leads & Accounts Enrichment** | Search for people and companies, and enrich their profiles | Full access, Custom, Off | | **Organization Databases** | Create and query shared databases managed by your organization. **Read only** limits it to read-only queries. | Full access, Read only, Custom, Off | | **Slack** | Send and read messages, reply in threads, send direct messages, react, search, list channels, and create channels and canvases | Full access, Read only, Custom, Off | | **Web Scrape** | Fetch and extract the contents of specific web pages | Full access, Off | | **Web Search** | Search the web for up-to-date information | Full access, Off | Who a coworker talks to in Slack, and which channels it can post in, are set separately on **Overview → Sharing**. See [Slack](https://docs.vybe.build/channels/slack.md). ## Browser, Calendar, Email and Meetings Four capabilities have their own section on the coworker's page, and you set them from that section's **Preferences** tab. They use the same access levels. | Capability | Where to set it | What it covers | | - | - | - | | **Browser** | **Browser → Preferences** | Using a real browser: open pages, click, type, extract content and take screenshots | | **Calendar** | **Calendar → Preferences** | Creating, updating and deleting events, responding to invites, and reading events | | **Email** | **Email → Preferences** | Sending, replying to and forwarding email, reading the inbox and attachments, and who can email the coworker. See [Email](https://docs.vybe.build/channels/email.md). | | **Meetings & transcripts** | **Meetings & transcripts → Preferences** | Joining meetings, listing and searching them, and reading transcripts. See [Meetings](https://docs.vybe.build/channels/meetings.md). | When one of these is **Off**, its section disappears from the sidebar. To turn it back on, type its name in the **Search agent settings…** box at the top of the coworker's page, for example "Email permissions", and open its preferences. ## Defaults | Setting | Default for a new coworker | | - | - | | Model | **Automatic model selection** on | | Capabilities, including Browser, Calendar and Meetings | **Full access** | | Email | On, but only the email address of the person who created the coworker can reach it, until you allow more contacts | | Integrations, MCP servers, custom APIs and external databases | Off, until you give the coworker access | ## Give a coworker access to connections Connecting a tool to Vybe doesn't give every coworker access to it. Each coworker starts with no access to your integrations, MCP servers, custom APIs or external databases, and you choose which ones it can use. You can do this in three ways: * **From the coworker's page.** Open its **Connections** section. The **Integrations** tab lists your connected accounts under **Access to Connections**, and the **MCP** tab lists them under **MCP servers**. Switch on the ones it should use, or click an account to choose **Full access**, **Read only**, **Custom** or **Off**. The **Advanced** tab has the **External Databases** and **Organization Databases** capabilities, plus your custom APIs, which you switch on or off. * **From the connection's settings.** In a private connection's settings, use **Agent access → Add agent** to give a coworker access. * **From a chat.** When a coworker needs a tool it can't use yet, it asks for access, and you approve. If you already have the account, its connect card shows **Grant**. If you connect a new private account from the coworker's chat, that coworker gets access automatically. Connections shared with your whole organization can be given to any coworker. A Private connection can only be given by the person who connected it. Switching on a private connection from a coworker's page starts it at **Read only**. For more on connecting tools and who can use them, see [Connections](https://docs.vybe.build/connections/overview.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.