> ## 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. # Sharing and access > Control who can talk to an AI coworker, who can manage it, and which apps it can work on Each AI coworker has its own access setting, separate from your organization role. It decides who can talk to the coworker and see its work, and who can change how it's set up. You choose a level when you create the coworker and can change it any time on the **Sharing** tab. ## Access levels | Level when creating | Same level on the Sharing tab | Who can use the coworker | | - | - | - | | **Anyone can talk to *name*** (default) | **Everyone at *organization*** | Everyone in your organization, except guests | | **Specific people** | **Only people invited** | The owner, the coworker's admins, and the people you add | | **You only** | **Private** | Only the owner | The owner is the person who created the coworker. Guests only get access to a coworker when someone adds them; on a coworker shared with everyone, use **Add guest** on the **Sharing** tab. People without access don't see the coworker in Vybe. If they ask it something in a Slack channel, it answers with an automated message saying they don't have access. ## What everyone with access can see Access to a coworker is access to its work. Everyone who can use a coworker can see: * **Chats.** Channels and threads in the coworker's **Chats** are shared. Everyone with access sees every conversation there, not just their own. * **Knowledge.** Its notes, skills and files. * **Artifacts.** Everything it has published. * **Activity.** The history of its runs, including what it was asked and how it replied. A coworker's settings are shared too. For example, changing the model in a coworker's chat changes it for everyone who uses that coworker. > [!WARNING] > > Don't put anything in a coworker's chats that shouldn't be seen by everyone with access to it. For private work, use a coworker set to **You only**. ## Change who can talk to a coworker **1. Open the Sharing tab** Open the coworker and go to **Overview → Sharing**. **2. Pick an access level** Under **Who can talk to *name*?**, choose **Everyone at *organization***, **Only people invited** or **Private**. **3. Add people (Only people invited)** Click **Add person**, search with "Search Slack users...", and pick someone. New people start with **Can chat**. **4. Set each person's role** Use the dropdown next to each person to choose **Can chat** or **Can edit**. Click **×** to remove someone. You add people from your Slack workspace, and they must also be members of your Vybe organization ("Add people from Slack who are members of your Vybe workspace"). If the coworker isn't in Slack yet, you'll see "Connect this bot to Slack to add people." See [Slack](https://docs.vybe.build/channels/slack.md). Only the owner or a coworker admin can change sharing. Everyone else sees "Only the owner or an admin can change sharing." ## Who can manage a coworker Under **Who can manage *name*?**: "The owner and admins manage settings, tools and sharing." The owner is listed first. To add another admin, click **Add admin** and pick someone. Admins can't be added to a **Private** coworker. Coworker roles are separate from organization roles. Being an Owner or Admin of your organization doesn't make you an admin of every coworker. ## Roles on a coworker | Role | Shown as | What they can do | | - | - | - | | Viewer | **Can chat** | Talk to the coworker in Slack and in Vybe, and see its chats, knowledge, artifacts and activity | | Editor | **Can edit** | Everything a Viewer can, plus change its capabilities and what it can access, link apps to it, and approve its access requests | | Admin | **Admin** | Everything an Editor can, plus change sharing and its Slack settings | | Owner | **Owner** | The person who created it. Same control as an Admin. | The owner and admins also get the coworker's problem reports and its [usage limit](https://docs.vybe.build/coworkers/usage-and-activity.md#monthly-usage-limit) emails. ## What your organization role allows Your [organization role](https://docs.vybe.build/organization/members-and-roles.md) decides what you can do with coworkers in general: | Organization role | AI coworkers | | - | - | | Owner, Admin, Editor | Create coworkers, and use the ones shared with them | | Viewer | Use coworkers shared with them, but can't create coworkers | | Guest | Can talk in Slack to coworkers they've been added to, but can't open coworkers in the Vybe web app | ## Slack settings on the Sharing tab Between the two sections, the **Sharing** tab also controls how the coworker behaves in Slack. These settings apply on top of the access level: "Slack channel and direct-message restrictions still apply." * **Only respond when @mentioned.** In channels and group DMs, the coworker only answers when someone @mentions it. Direct messages aren't affected. * **Direct messages.** Turn direct messages to the coworker on or off. * **Direct group messages.** Who can include the coworker in group DMs. With a limit set, it "Only replies if every member of the group is allowed." * **Channels.** The channels the coworker has joined. For each one, choose **Read**, **Read and write** or **Leave channel**. Use **+ Add channel** to add it to another channel. The list also shows the access new channels get, such as "Channels this agent is added to get read access by default." New channels get your organization's default access. Owners and Admins set it with **Default access** under **Slack channel access** in **Settings → Organization → General**: **Read** (the default), where someone has to grant write access for each channel, or **Read and write**, where the coworker can post without an extra approval. The default applies when the coworker's owner, an admin or someone with **Can edit** invites it to a channel in Slack or adds a channel with **+ Add channel**. When anyone else invites it, the channel starts at **Read**. Channels the coworker is already in keep their current access. For a coworker that isn't shared with everyone, Vybe warns: "Everyone in a channel sees this agent's replies there. Only people with access can ask it things." See [Slack](https://docs.vybe.build/channels/slack.md) for the details of each setting. ## Link apps to a coworker A coworker can work on the Vybe apps you link to it. Linking lets it change the app's code, publish it, read its database and call its API. 1. Open the coworker and go to **Overview → Apps**. 2. Under **Access to Apps**, switch on each app the coworker should work with. Use "Search apps…" to find one. You'll see "App linked" or "App unlinked". Apps a coworker creates are linked to it automatically. The coworker's owner, admins and editors can change links. See [Apps](https://docs.vybe.build/apps/overview.md). ## Hide coworkers and apps from the sidebar If most of your organization only talks to coworkers in Slack, you can simplify the Vybe sidebar. In **Settings → Organization → General**, turn off **AI coworkers and apps** ("Show AI coworkers and apps in the sidebar for everyone in this organization"). This hides the **AI coworkers** and **Apps** links and the coworker list from the sidebar for everyone. **New AI coworker** stays. It only changes the sidebar: it doesn't change who can access any coworker or app. ## Pin coworkers Pin the coworkers you use most so they stay at the top. Hover a coworker in the sidebar and click the pin icon (**Pin *name***), or use **Pin** in its **…** menu on the **AI coworkers** page. Pinned coworkers appear in a **Pinned** section of the sidebar and first on the **AI coworkers** page. Pins are personal. Pinning doesn't change anyone else's sidebar or anyone's access. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.