Box as the Content Layer for Slack

Box as the Custom Files Store in Slack enables you to use Box to securely store all files uploaded in your Slack conversations. Box as the Custom Files Store in Slack is also available on mobile devices, so you can share content even on-the-go.

By enabling the Custom Files Store feature:

• Uploaded local files go directly to Box through the Slack interface without passing through Slack servers.
• Uploaded content resides in a Box folder associated with a given Slack private channel, public channel, or direct message conversations (chats).

Custom Files Store is best suited for customers who use Box within a specific Slack workspace/organization. Users without Box accounts will not be able to upload content, including screenshots or images, into Slack.

Mapping of Slack channels to Box folders

As soon as a user uploads a file into a Slack channel, Box for Slack creates a folder associated with this channel, and adds a Slack bookmark called Channel files. The folder is named the same as its associated channel. The parent folder is associated with the channel’s Slack Workspace, and the root folder is named Slack Channel files. Additionally, workspace and channel sharing folders define the mapping structure, each following the first character of the name. For example:

• All Files
  • Slack Channel Files
    • Workspace X
      • XYZ
        • Channel B
          • business-analytics
          • business-dev
        • Channel C
          • cc-team

Mapping between Slack channels and Box folders also applies to users: channel members who have authorized the Box for Slack app become editing collaborators of the associated Box folder.
This mapping is maintained up-to-date by the Box for Slack app. Changes in Slack reflected in Box include:

• Added and removed channel members.
• Channels moved to a different Workspace, renamed or deleted.
• Uploaded files deleted in Slack.

For large channels (1000 or more members), the most common purpose of file sharing is to broadcast information rather than to invite to collaborate on editing its contents. Therefore, the folder for channels of 1000 or more members have a generated Shared Link in People in your company can view mode instead of channel members set as editing collaborators.

For direct message conversations (chats), the upload folders will be created in the Slack Conversation Files root folder, inside the personal folder of the user who was the first uploader in the given conversation.

For example:

• All Files
  • Slack Channel Files,
  • Slack Conversation Files,
    • User ...001
      • John Smith - Slack Files,
        • XYZ
          • Kevin Marek, John Smith

where

• User ...001 is an example subfolder for all enterprise users whose Box user ID ends with ‘001’ digits,
• XYZ is an example Slack Workspace name.

Eligibility:

• Your organization must have a Slack-assigned CSM.
• Your organization must be a paid Box business account with access to the Box admin console.

Recommended settings when using Custom File Store with Box

• Shared Links should be enabled for folders.
• People in your company should be allowed to access Shared Links. (People in your company can view/edit should be an available option, when creating shared links)
• Shared Links auto-expiration should not be enforced. 
• If multi-workspace channels are used, organization-wide installation of Slack is recommended, with Box for Slack installed in each workspace. An organization-wide installation of Box for Slack is recommended if your organization has channels belonging to multiple workspaces at the same time.
• Users belonging to different segments should not be allowed to join the same channels in Slack.

Deploying Box as the content layer in Slack

Deploying Box as the content layer in Slack is a three-part process in the Admin Console, followed by a manual enablement required by Slack:

1. Entering the Slack Organization and/or Workspace ID or IDs in the Box for Slack app configuration.
2. Authorizing the Box for Slack app to use Box as Slack file storage.
3. Ensuring the latest version of Box for Slack is installed in your Slack Organizations and/or Workspaces.

To enter the Slack Organization ID in the Box for Slack integration

1. Log into the Box Admin Console as a Box Admin. 
2. Go to Apps > Box Apps & Integrations.
3. Scroll down to the Individual Application Control section.
4. Search for Box for Slack.
5. On the right-hand side, click Configure. 
6. Scroll down to the Box content layer settings, then enter the relevant Slack Organization IDs and/or Workspaces in the Restrict to specific Slack Enterprise Grid Org ID allowlist / Slack Workspaces allowlist text fields.

To authorize the Box for Slack app to use Box as Slack file storage

1. Go to Apps > Custom Apps Manager.
2. Click Add App.
3. In the Client ID field, enter: 0x3vedms8thsqqkphx49cgc5c03n6wj5.
4. Click Next.
5. Review the information, then click Authorize. 
6. You should now see Box as File Storage for Slack in the Apps list

To ensure the latest version of Box for Slack is installed in your Slack Organizations and/or Workspaces:

Install the latest version by following this link.

If Box for Slack is installed org-wide, you can also:

1. Open the Slack admin console, and go to Integrations.
2. In the Manage apps dropdown, select Install app.
3. Search for "Box" and continue through the installation flow.

Removing Box as the content layer in Slack

1. Contact your Slack-assigned CSM to request Custom File Store deactivation for your specific Slack organization IDs and/or workspaces.
2. Optionally remove the Slack Organization IDs and/or Workspaces in the Restrict to specific Slack Enterprise Grid Org ID allowlist / Slack Workspaces allowlist text fields. (Step 6 above)
3. Optionally disable the Box as File Storage for Slack app in the Custom Apps Manager list. (Step 4.6 above)