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

# Juicebox for Slack

> Bring Juicebox notifications and profile actions into the Slack channels where your recruiting team already collaborates.

## Overview

Recruiters and hiring managers already coordinate on roles in Slack, but candidate profiles live in other tabs.

Juicebox for Slack closes that gap: connect a Project or Agent to the channel where the team works, and updates show up at the right time — right in the thread, ready to act on.

Juicebox for Slack lets you:

* **Notify, answer, and act** on existing projects, sequences, and Agents
* **Review and surface leads** produced by an existing Agent or shortlist
* **Act faster** on common actions — especially on mobile

## Set up in three steps

<Note>
  A paid Slack plan is required to use the Juicebox AI agent in the Slack app container. All other Juicebox for Slack features work on free Slack plans, including channel notifications, lead review carousels, and `@Juicebox` mentions in channels and threads.
</Note>

<Steps>
  <Step title="Connect Slack to Juicebox">
    Navigate to the **Integrations** tab and connect the Slack integration to Juicebox. This creates a single workspace connection.

    Each Juicebox organization connects to exactly one Slack workspace, and each Slack workspace connects to exactly one Juicebox organization. Juicebox blocks a connect that would replace an existing pairing. This happens when the workspace already belongs to another Juicebox organization, or when your organization is already connected to a different workspace. Disconnect the existing pairing first, then try again. Re-authorizing the same organization and workspace still works and is safe to run to refresh permissions.
  </Step>

  <Step title="Link a project or Agent">
    From the **Projects** page, click the project's **Slack** row to open the Slack dialog, then pick a channel from the searchable picker. For a private channel, paste its channel link or ID into the picker instead.

    To link a channel, from Juicebox or from Slack, you need two things:

    * Your Juicebox account is linked to your Slack account. Run `@Juicebox account` in any channel Juicebox is in. See [Connect a Slack identity to a Juicebox account](#connect-a-slack-identity-to-a-juicebox-account).
    * You're a member of the channel.

    If you link a private channel before you invite Juicebox to it, nothing posts there yet. See [Muted channel connections](#muted-channel-connections).
  </Step>

  <Step title="Tag @Juicebox in the Slack channel">
    Get started by asking Juicebox what it can do in Slack.

    Type:

    ```text theme={null}
    @Juicebox, what can you do?
    ```

    Juicebox is added to the channel and starts surfacing notifications, project updates, and shortlist review requests there. For a private channel, invite `@Juicebox` to the channel first so it can reply to mentions and thread follow-ups.
  </Step>
</Steps>

## Core capabilities

### Review leads directly in Slack channels

When a review is requested, Slack posts a candidate carousel: approve, skip, or reject each profile.

* Add context during the decision; feedback syncs back and informs the Agent's learning and the platform.
* Carousels hold up to 10 cards, and press **See More** to generate more profiles at the end of the carousel.
* Shortlist reviews and Agent leads follow the same flow.

### Get project and sequence notifications

Once a Project is connected to a Slack channel, activity shows up in that channel:

* New Agent leads ready for review, or interested replies from an email sequence
* Project activity such as name changes or collaborators being added or removed
* Project activity summaries on a configurable cadence

You can also chat directly with Juicebox in Slack to get project notifications and status updates.

### Ask @Juicebox for project and Agent analytics

Tag `@Juicebox` in your Slack Chat to get quick answers without navigating dashboards:

* Pending, approved, or reviewed lead counts at a glance
* Outreach volume, such as how many people were contacted or added to a sequence
* Pipeline, project, Agent, or sequence health, answered in the thread
* What happened to a profile after it was approved

<Note>
  Juicebox uses LLMs that have the potential to generate inaccurate results.
</Note>

#### What Slack analytics can answer on your plan

Slack mirrors the same analytics access rules as the Juicebox web app, so what `@Juicebox` will answer depends on your plan and role.

**Open on every paid Juicebox plan (any Juicebox member in the channel can ask):**

* A project's pipeline by stage, candidate lists, and shortlist activity
* Agent health listings, such as which Agents are paused or out of leads
* Project-scoped counts, such as how many candidates were shortlisted for a specific project
* All outreach analytics, including emails sent per teammate and sequence performance

**Juicebox Business plan and analytics access required:**

* Searches run per recruiter and profiles viewed
* Per-teammate leaderboards, such as who shortlisted the most candidates
* Cross-project shortlist rollups, such as shortlisted candidates per project without naming a project
* Org-wide project and Agent counts, such as how many Agents you have

To ask these usage questions in Slack, you need a Juicebox Business plan and one of the following roles: admin, read-only admin, or the `analyticsAdmins` role granted per member from **Settings → Team members**.

### Manage notifications from Slack

Configure which Juicebox notifications a channel receives without leaving Slack. In any channel connected to a project or Agent, run:

```text theme={null}
@Juicebox settings
```

Juicebox posts a launcher that opens an in-Slack configuration modal for the projects and Agents linked to that channel. From the modal you can:

* **Mute all notifications** for the project or Agent in this channel
* **Choose which notification groups fire** — for example, new leads, sequence replies, or project activity
* **Disconnect** the project from this channel. Juicebox posts a message in the thread so the channel knows why updates stopped.

Changes made in Slack stay in sync with the notification settings on the web, so you can manage the same connection from either surface. Muting keeps your group selections intact, so unmuting restores your previous choices. The project activity summary schedule (daily, weekly, or monthly digest) is unchanged and continues to follow the cadence set in Juicebox.

Before the modal opens or a change is saved, Juicebox checks that your Slack account is linked to a Juicebox user and that you have permission to manage the project or Agent. If you don't, Juicebox posts a private message in the channel explaining why instead of opening the modal.

If no project is connected to the channel, `@Juicebox settings` asks you to connect one first. See [Connect or move a project from Slack](#connect-or-move-a-project-from-slack).

### Connect or move a project from Slack

Ask `@Juicebox` about a project's channel from any channel Juicebox is in:

```text theme={null}
@juicebox, where does [Project] post its updates?
@juicebox, connect [Project] to this channel.
@juicebox, change the Slack notifications for [Project].
```

Juicebox replies with a card that shows where the project posts:

* **Not connected:** click **Connect to this channel**, then click **Connect**.
* **Posts to this channel:** click **Notification settings** to mute, change notification groups, or disconnect.
* **Posts to another channel:** click **Move to this channel**. Your notification choices move with it.

You need the same [access as when you link a channel](#set-up-in-three-steps). Juicebox confirms the change in the thread. Ask from a channel, not a DM.

### Take profile actions and create tasks

Manage profiles and follow-up straight from Slack:

* Add a **note** or update **tags** on a profile
* Create a **reminder or task** and assign it to a teammate in the channel — the assignee is tagged in Slack, and the task and note live in Juicebox
* Share a **LinkedIn URL** and add it straight to a project shortlist

### Read notes on a contact

Ask `@Juicebox` about a candidate's notes to see what your team has written about them:

```text theme={null}
@juicebox, what notes do we have on [Candidate]?
@juicebox, any recruiter notes on https://www.linkedin.com/in/ada-lovelace?
```

Juicebox returns written notes only, not activity such as profile views, exports, or sequence adds. Notes come from two sources, merged into one list with the newest first:

* **Juicebox notes** your team added in Juicebox, from the projects you can access. Name a project to narrow these to that project.
* **ATS notes** recruiters wrote in your connected ATS. This applies to Ashby and to ATSes connected through Kombo. See [ATS Integrations](/ats-integrations). ATS notes are org-wide, so naming a project doesn't filter them.

Each note shows its source and author, for example "In Ashby, Jordan wrote…". Juicebox doesn't show private ATS notes, or any ATS notes on candidates who are hired or marked private in the ATS. If Juicebox can't reach your ATS, it still returns your Juicebox notes.

### Work with searches from Slack

Ask `@Juicebox` to browse, review, create, or edit the searches inside a project without leaving Slack. These tools operate on ordinary searches; for Agents, see [Manage an Agent from Slack](#manage-an-agent-from-slack).

**Browse and review (read-only)**

Available to any licensed Juicebox user connected to Slack.

* **List searches** — show the searches in a project, optionally filtered by a title fragment. Returns each search's title, execution state, last-updated timestamp, and Juicebox link.
* **Inspect a search** — read one search's filter summary, criteria, execution state, and canonical link. Accepts a search ID, exact or partial title, or a canonical Juicebox search URL. Ambiguous titles return candidates so you can confirm which one you meant.
* **See profiles** — return up to five candidates from the most recent completed run of a search. This never re-runs the search or marks profiles as viewed. If no run has finished yet, Juicebox says the results aren't cached instead of executing one.

**Create and update**

Available to regular and admin licensed seats on non-Agent projects. Hiring-manager, sequence, read-only-admin, and guest accounts get read-only access at most.

* **Create search** — paste a role brief or job description. Juicebox builds filters and criteria, saves the search in the project you name, and runs it immediately. The response includes the search link, pool size, first-page count, and up to five candidates. If the source looks like a job description, Juicebox uses JD mode automatically.
* **Update search** — apply a natural-language edit to one existing search and re-run it.

Example prompts:

```text theme={null}
@juicebox, list searches in [Project].
@juicebox, show me the filters on the "Staff PM - NYC" search.
@juicebox, create a search in [Project] for a senior backend engineer with Go and Kubernetes based in the EU.
@juicebox, in [Project], update "Staff PM - NYC" to also include product-led-growth experience.
```

Search writes are gated on licensed-seat projects.

### Export a candidate to your ATS from Slack

Ask `@Juicebox` to send a candidate straight into your connected ATS without leaving the channel. This is available in any channel where Juicebox is present, once your organization has an ATS integration connected from the **Integrations** tab. See [ATS Integrations](/ats-integrations) for the list of supported providers.

Give Juicebox the candidate's Juicebox profile URL or LinkedIn URL and the job you want them on. Juicebox proposes the specific candidate, job, and stage before writing to your ATS, so you can confirm before the export runs.

```text theme={null}
@juicebox, add https://www.linkedin.com/in/ada-lovelace to our "Staff Backend Engineer" role in Ashby.
@juicebox, export [Candidate] to the Senior PM req in Greenhouse, at the Recruiter Screen stage.
@juicebox, put https://www.linkedin.com/in/ada-lovelace in our general talent pool.
```

Behind the scenes, Juicebox uses three tools to complete the export:

* **Find a job** — Juicebox searches your ATS's open jobs by the title or requisition code you mentioned. If more than one job matches, it lists the options and asks which one; if nothing matches, it says so and offers to browse.
* **Find a stage (optional)** — if you asked for a specific pipeline stage, Juicebox lists the stages on the chosen job in pipeline order and confirms which one you meant. Skip this to let the candidate land in the job's default first stage. Stages for jobs you can't see in the ATS are hidden.
* **Export the candidate** — Juicebox writes the candidate to the ATS on the confirmed job and stage, and links back to their record in the ATS when the export finishes.

A candidate who isn't in Juicebox yet can still be exported. If you share a LinkedIn URL that Juicebox doesn't have on file, Juicebox creates the contact as part of the export and tells you it added them.

Where the ATS supports it, you can also export to a general talent pool with no specific job. Say so explicitly (for example, "add to the general pool"). If the connected ATS requires a job, Juicebox tells you and asks you to pick one.

#### Guards that apply to Slack exports

Slack exports reuse the same export pipeline as the Juicebox web app, so the same rules apply:

* **Export credits** — each successful export spends an org export credit. Exports fail with a clear message when the org has used up its credits for the billing period.
* **Contact-info policy** — if your organization requires an email or phone number before exporting, Juicebox blocks the export when neither is on file for the candidate.
* **Restricted-domain policy** — candidates whose contact email is on a domain your organization has restricted are blocked.
* **Duplicate detection** — if the candidate is already in the ATS (matched by LinkedIn URL), Juicebox says so and links to their existing record instead of exporting again.
* **Plan and seat gating** — Slack exports require a paid Juicebox plan and a licensed seat. Free-plan users, unlicensed seats, and Slack guests are blocked with an explanation.

Every Slack export shows up in your normal **Profile Export History** in Juicebox, tagged as coming from Slack. See [Exports](/exports) for the full export workflow, credit behavior, and history view.

### Create an Agent from Slack

Ask `@Juicebox` to create an Agent from the thread you're in. Include the role, seniority, and location, or paste a job description. Juicebox creates the Agent, starts calibration in the thread, and links the channel so updates post there. If you don't meet the [requirements to link a channel](#set-up-in-three-steps), or you ask from a DM, Juicebox still creates the Agent. Link the channel later from the project's **Slack** row. Requires a licensed Juicebox seat.

If the channel is linked to one project that doesn't have an Agent yet, Juicebox asks whether to add the Agent to that project or create a new project. Reply with your choice, and Juicebox creates the Agent there.

* **Existing project:** Juicebox adds the Agent to the linked project. The channel is already linked, so Juicebox doesn't re-link it or post another welcome message. If Juicebox can't add the Agent to that project, for example because it got an Agent in the meantime, Juicebox creates a new project instead.
* **New project:** Juicebox creates a new project for the Agent and links the channel to it.

If the channel's linked project already has an Agent, or the channel is linked to more than one project, Juicebox creates a new project without asking. Each project holds one Agent.

```text theme={null}
@juicebox, create an Agent for a senior backend engineer with Go and Kubernetes in the EU.
@juicebox, create a new Agent for [Project role] and add [Teammate] as a collaborator.
```

### Manage an Agent from Slack

Ask `@Juicebox` to pause, resume, close, or reopen an existing Agent, and to change its approval type, destination for approved leads, or daily lead volume. Juicebox confirms the change before applying it. Requires a licensed Juicebox seat. Agent search criteria and calibration stay in Juicebox.

```text theme={null}
@juicebox, pause the Agent for [Project].
@juicebox, switch [Project]'s Agent to manual approval.
@juicebox, set [Project]'s Agent to 15 leads a day.
```

### Channel reachability

If a linked channel needs Juicebox to be invited before it can reply to mentions and thread follow-ups, the Slack dialog says so under the channel picker. Run `/invite @Juicebox` in the channel, then click the refresh icon next to the picker.

If the channel is archived, the dialog surfaces that instead and asks you to pick another channel. See [Archived Slack channels](#archived-slack-channels).

### Muted channel connections

A channel connection stays muted until Juicebox can confirm that the person who connected the channel is in it. While it's muted, nothing posts to the channel. The project's Slack dialog shows a warning that says so.

To fix it:

* For a private channel, run `/invite @Juicebox` in the channel, then refresh the Slack dialog.
* If the person who connected the channel left it, they rejoin it. Or you can disconnect the channel and connect it again yourself.

Inviting Juicebox doesn't help if the person who connected the channel isn't in it.

### Disconnect a project from its Slack channel

If a project was linked to the wrong Slack channel, or you no longer want notifications for it in Slack, you can unlink it from the project's configuration without leaving the flow.

1. Open the project and click the **Slack** row that shows the connected channel name.
2. In the dialog, click **Disconnect** next to the channel name.
3. Confirm **Disconnect** in the prompt.

You can also disconnect from Slack. Run `@Juicebox settings` in the channel, click **Disconnect**, and confirm.

Notifications stop immediately, and Slack guests in that channel lose the ability to ask `@Juicebox` about this project. Disconnecting clears your notification settings for this project, so if you reconnect the project to a channel later, notifications start from the defaults.

To disconnect the entire workspace instead of a single project:

1. Go to **Integrations**.
2. On the Slack card, click **Manage connections**.
3. In the dialog, click **Options** > **Remove all connections**.
4. Confirm **Remove all connections** in the prompt.

This removes the Slack integration from your organization and disconnects it from every project and Agent, so a different workspace can be connected. You can reconnect Slack at any time.

### Archived Slack channels

If a Slack channel linked to a Juicebox project or Agent is archived, Juicebox marks the connection inactive and stops sending notifications to that channel. Your notification preferences and the connection record are preserved. To resume delivery with the same settings, reconnect the project or Agent to a channel from the **Projects** page.

### Slack guests

A Slack guest is a channel member Juicebox can't match to a licensed Juicebox user. Guests can see Juicebox messages in the channel and ask project-scoped questions about the channels they're in, but can't run cross-project or usage analytics.

Guests can:

* Read notifications, review requests, and replies Juicebox posts in the channel
* Ask `@Juicebox` for pipeline, candidate lists, Agent health, and outreach questions about the projects their channel is linked to. Juicebox automatically scopes the answer to those projects.
* Ask general questions about how Juicebox works (for example, "how does Juicebox work?")

Guests can't:

* Ask `@Juicebox` for usage analytics such as searches run, profiles viewed, per-teammate leaderboards, or org-wide project and Agent counts
* Take profile actions, add to shortlists, or create tasks

When a guest asks a question that would require a Juicebox seat, Juicebox replies with a guest-specific message that names the missing membership and offers to have someone invite them to Juicebox. The reply also points at the `@Juicebox account` command, so a teammate whose Slack email doesn't match their Juicebox email can connect the two themselves.

### Connect a Slack identity to a Juicebox account

Juicebox matches Slack members to Juicebox users by email. If a teammate's Slack email doesn't match the email on their Juicebox account, they can connect the two identities themselves without an admin.

When Juicebox can't match a Slack user by email, it sends them a private message only they can see, with a **Sign in to Juicebox** button. Anyone can also trigger the same message on demand by typing `@Juicebox account` (or `@Juicebox find my account`) in any channel where Juicebox is present.

After clicking the button, they sign in to Juicebox, confirm which Slack identity and Juicebox account will be connected, and finish the link. Juicebox then treats the two identities as the same person for permissions, assignments, and notifications.

If they're already linked, `@Juicebox account` confirms who they're connected as. The link only works within your Juicebox organization.

## Actions to try in Slack

| Action | Example prompt |
| - | - |
| Notification settings | `@juicebox settings` |
| Connect or move a project's channel | `@juicebox, connect [Project] to this channel.` |
| Connect your Juicebox account | `@juicebox account` |
| Lead review | `@juicebox, show me the pending leads for [Agent].` |
| Agent status | `@juicebox, how is [Agent] doing?` |
| Create an Agent | `@juicebox, create an Agent for a senior backend engineer with Go and Kubernetes in the EU.` |
| Manage an Agent | `@juicebox, pause the Agent for [Project].` |
| Approvals | `@juicebox, how many leads did we approve this week for [Project]?` |
| Outreach | `@juicebox, how many people have we contacted in [Sequence]?` |
| Profile history | `@juicebox, what happened to [Profile] after we approved them?` |
| Contact notes | `@juicebox, what notes do we have on [Profile]?` |
| Shortlist add | `@juicebox, add this LinkedIn profile to the shortlist for [Project].` |
| Export to ATS | `@juicebox, add [Candidate] to our "[Job title]" role in [ATS].` |
| Pipeline health | `@juicebox, what is the current health of [Project]?` |
| Task | `@juicebox, assign [Teammate] a task to follow up with [Profile] by Friday.` |
| List searches | `@juicebox, list searches in [Project].` |
| Inspect a search | `@juicebox, show me the filters on the "[Search title]" search in [Project].` |
| Create a search | `@juicebox, create a search in [Project] for [role brief or JD].` |
| Update a search | `@juicebox, in [Project], update "[Search title]" to also require [criterion].` |

## Slack permissions requested

When you connect Slack, Juicebox requests the following scopes:

| Permission | Purpose |
| - | - |
| `app_mentions:read` | Detect when a user starts a request with @Juicebox, so Juicebox knows when to respond. |
| `assistant:write` | Show Juicebox as a Slack AI assistant and show progress while it processes a request. |
| `channels:history` | Read messages in public channels where Juicebox is present, so it can understand and answer requests. |
| `channels:read` | Identify public channels, so Juicebox can maintain the correct project-to-channel connection. |
| `channels:manage` | Create a public channel when a user chooses to create one for a Juicebox project or Agent. |
| `channels:write.invites` | Invite selected project members to a public channel that Juicebox creates. |
| `chat:write` | Send replies, notifications, and review requests as Juicebox. |
| `chat:write.public` | Send a message to a connected public channel when Juicebox is not yet a channel member. |
| `files:read` | Read supported files shared where Juicebox is present, so it can use them when answering a request. |
| `files:write` | Upload files or images that Juicebox includes in a Slack response. |
| `groups:history` | Read messages in private channels where Juicebox is present, so it can understand and answer requests. |
| `groups:read` | Identify private channels where Juicebox is present, so it can maintain the correct project-to-channel connection. |
| `groups:write` | Create a private channel for a confidential Juicebox project or Agent. |
| `groups:write.invites` | Invite selected project members to a private channel that Juicebox creates. |
| `im:history` | Read direct messages with Juicebox, so it can understand the conversation and answer follow-up questions. |
| `im:read` | Identify direct-message conversations with Juicebox, so it can reply in the correct conversation. |
| `im:write` | Start a direct message when Juicebox must send a private response. |
| `links:read` | Detect Juicebox links in messages, so it can determine whether a preview is available. |
| `links:write` | Show a preview for supported Juicebox links. |
| `mpim:history` | Read group direct messages where Juicebox is present, so it can understand and answer requests. |
| `mpim:read` | Identify group direct messages where Juicebox is present, so it can reply in the correct conversation. |
| `reactions:read` | Read reactions on Juicebox messages, so it can recognize existing feedback or status. |
| `reactions:write` | Add or remove a reaction to acknowledge a request or show its status. |
| `users:read` | Identify Slack members, so Juicebox can use the correct names, mentions, assignments, and invitations. |
| `users:read.email` | Match a Slack member to the correct Juicebox user for access checks, assignments, and invitations. |

## Best practices

* The integration creates one workspace connection, but supports unlimited Slack channel to project or Agent mappings. We recommend **one channel per project or Agent**, though some teams put everything in a single channel.
* Notifications are scoped to the channel — anyone in the channel gets them. Some notifications (project renamed, collaborators added or removed) can't be disabled. The project activity summary has a configurable cadence — it defaults to weekly, and can be set to daily or monthly.
* You only need to tag `@Juicebox` when starting a new thread, not on every message within the thread.
* DMing Juicebox directly works for status and analytics questions, and works for users without a Juicebox seat (view-only). Lead review cannot happen in DMs.

## FAQ

<AccordionGroup>
  <Accordion title="Can anyone in my Slack workspace connect Juicebox to a channel?">
    Connecting the Slack workspace to Juicebox is a one-time setup done from the **Integrations** tab in Juicebox, and requires a Juicebox admin. Non-admins see the **Connect to Slack** button but can't use it.

    Once the workspace is connected, anyone with access to a project can link it to a Slack channel from the **Projects** page. See [what you need to link a channel](#set-up-in-three-steps).

    Any Slack member of a channel can add the bot to that channel by tagging `@Juicebox` or running `/invite @Juicebox`. If your Slack workspace restricts who can add apps to channels, that restriction applies here too.
  </Accordion>

  <Accordion title="Can I get in touch with Juicebox's team?">
    Yes. Email [support@juicebox.ai](mailto:support@juicebox.ai) for product and account questions, or [sales@juicebox.work](mailto:sales@juicebox.work) for plan and pricing questions.
  </Accordion>

  <Accordion title="How can I access additional support for this integration?">
    Email [support@juicebox.ai](mailto:support@juicebox.ai) with details about your Juicebox organization, the Slack workspace, and what you're seeing.
  </Accordion>

  <Accordion title="How does the integration collect, manage, and store candidate data?">
    Juicebox for Slack surfaces candidate data that already lives in your Juicebox organization. It does not collect candidate data from Slack, and it does not use messages in your Slack workspace to build the Juicebox candidate database.

    For details on how Juicebox handles data, see the [Juicebox privacy policy](https://juicebox.ai/privacy-policy) and the [Data Sources](/data-sources) page.
  </Accordion>

  <Accordion title="Slack notifications aren't showing up in my channel after installing this integration">
    Check each of the following:

    1. The project or Agent is linked to that specific channel. Open the project and look for the **Slack** row — it should show the channel name.
    2. Juicebox has been added to the channel. Tag `@Juicebox` or run `/invite @Juicebox` in the channel to add it. See [Channel reachability](#channel-reachability) if the project's Slack row asks you to invite Juicebox.
    3. The project's Slack dialog doesn't warn that nothing posts to the channel. If it does, see [Muted channel connections](#muted-channel-connections).
    4. Notifications for the project aren't muted. Run `@Juicebox settings` in the channel and confirm the relevant notification groups are on.
    5. The channel hasn't been archived. Archiving a linked channel marks the connection inactive and stops delivery.

    If notifications still don't arrive, email [support@juicebox.ai](mailto:support@juicebox.ai).
  </Accordion>

  <Accordion title="Why doesn't the candidate preview in Slack match what I see in Juicebox?">
    Slack cards show a compact summary of a candidate. The full profile — including all criteria, sources, and history — lives in Juicebox. Open the profile link in the Slack card to see everything Juicebox has on that candidate.
  </Accordion>

  <Accordion title="Can I restrict which channels the Juicebox bot is allowed to post in?">
    Juicebox only posts in a channel after it has been added to that channel and a project or Agent has been linked to it. To stop Juicebox from posting in a specific channel, either disconnect the project from that channel or remove Juicebox from the channel in Slack.

    To disconnect a project from its channel:

    1. Open the project and click the **Slack** row that shows the connected channel name.
    2. In the dialog, click **Disconnect** next to the channel name.
    3. Confirm **Disconnect** in the prompt.

    To remove Juicebox from a channel entirely, use Slack's **Remove app** action on the channel.
  </Accordion>

  <Accordion title="What OAuth scopes does Juicebox request, and can I limit them?">
    See [Slack permissions requested](#slack-permissions-requested) above for the full list of scopes and what each one is used for. All listed scopes are required for the integration to work as documented — you can't remove individual scopes during install.

    If your organization needs a narrower permission set, email [support@juicebox.ai](mailto:support@juicebox.ai) to discuss what's possible.
  </Accordion>
</AccordionGroup>