With the Box for Slack integration, you can also use Box as the Custom Files Store in Slack, where Box acts as the single content layer supporting all your conversations on Slack. That is, Box becomes the one place where all files uploaded in Slack are stored, and stored securely. This enables admins to manage all their company's content in one secure platform and gives security teams peace of mind. This functionality is also available on mobile devices, so you can share content even on-the-go.
Custom Files Store is the term Slack uses to indicate files shared in Slack channels and conversations are stored in Box.
By enabling the Custom Files Store feature:
- User uploads of local files route 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 or public channel,
- or, in the case of Direct Messages (conversations), a Box folder named Slack Chat Files, which is either owned by the uploader or that the uploader has Editor permissions to, depending on your organization's Content Creation settings.
This feature is best suited for customers who are wall-to-wall Box, or are wall-to-wall Box within a specific Slack workspace/organization. Users without Box accounts will not be able to upload content, including screenshots or images, into Slack.
A private Slack Chat Files folder is also used for uploaded content in the following cases:
- Multi-party direct messages (group chats),
- Slack Connect channels,
- Large channels of 1000 or more members, if People in the company Shared Links to folders is disabled or enforced to auto-expire.
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. Its parent folder is a folder associated with the channel’s Slack Workspace, and the root folder is named Slack Channel files. Additionally, workspace and channel sharing folders are used in the mapping structure, each following the first character of the name. For example:
- All Files
- Slack Channel files
- Workspace A
- Channel B
- Channel C
- Channel B
- Workspace A
- Slack Channel files
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 that will be reflected in Box include:
- Added and removed channel members
- Channel moved to a different Workspace, renamed or deleted
- Uploaded file deleted in Slack
Slack message and file retention policies will not be automatically applied to the content stored in Box. We recommend setting a Box retention policy for Slack folders independently.
For large channels of 1000 members or more, the most common purpose of file sharing is to broadcast information rather than to invite to collaboration editing its contents. Therefore, the folder for channels of 1000 members or more have a Shared Link in People in your company can view mode generated instead of channel members set as editing collaborators.
- 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:
- Entering the Slack Organization and/or Workspace ID or IDs in the Box for Slack app configuration
- Authorizing the Box for Slack app to use Box as Slack file storage
- Ensuring the latest version of Box for Slack is installed in your Slack Organizations and/or Workspaces
Ensure that the Box for Slack app is installed in the relevant Slack Organizations and/or Workspaces. (Note: the "Box File Picker" and "Share to Slack in Box" are separate integrations not relevant to the Custom Files Store enhancement.)
To enter the Slack Organization ID in the Box for Slack integration
- Log into the Box Admin Console as a Box Admin.
- Go to Apps > Box Apps & Integrations.
- Scroll down to the Individual Application Control section.
- Search for Box for Slack.
- On the right-hand side, click Configure.
- 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
- Go to Apps > Custom Apps Manager.
- Click Add App.
- In the Client ID field, enter:
- Click Next.
- Review the information, then click Authorize.
- 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:
- Open the Slack admin console, and go to Integrations.
- In the Manage apps dropdown, select Install app.
- Search for "Box" and continue through the installation flow.
Note: To fully complete deployment of this feature, there is a manual enablement step required by Slack. Please reach out to your Slack CSM to complete enablement.
Removing Box as the Content Layer in Slack
- Contact your Slack-assigned CSM to request Custom File Store deactivation for your specific Slack organization IDs and/or workspaces.
- 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)
- Optionally disable the Box as File Storage for Slack app in the Custom Apps Manager list. (Step 4.6 above)