Techila
Techila/Integrations/Box integration.
Bx
[ Productivity ]Box for SalesforceAppExchange package

Box
Salesforce integration.

What Box for Salesforce does, who can use it, how it is installed, and what to plan before you switch it on.

Request an integration map →Download the spec sheet →

The Salesforce Box integration is Box for Salesforce, Box's managed package on AppExchange. It lets users share, access and manage Box content from Salesforce, with a Box folder tied to each record. Box says it is available at no extra charge for joint Box Enterprise and Salesforce customers. Users need both a Box and a Salesforce account.

[ How it works ]

Which Salesforce records can show Box folders?

Box says Lightning record pages for Lead, Account, Contact and Opportunity come preconfigured with the Box component, and you can add it to other standard or custom objects.

[ The connector ]

Files in Box, work in Salesforce.

Techila Global Services is a Salesforce Summit partner. We install and configure Box for Salesforce: the service account, root folder, permission sets, page layouts and permission sync.

We test in a sandbox first and support the set-up after launch.

Storing files in Microsoft 365 instead? See SharePoint and Salesforce.

What does Box for Salesforce do?

Box's support article lists these parts of the integration. Folders are tied to specific Salesforce records, and record folders sit inside one root folder owned by a Box service account.

Features of Box for Salesforce
FeatureWhat Box says it does
Record foldersEmbedded folder widgets on standard or custom records
Box Files, Box Settings and Box Sign tabsAccess files, configure the integration, and set up e-signature
Box ExtractPulls structured data from Box documents to create or update Salesforce records
Box EventsRecords Box user activity on Salesforce records
Box Federated SearchLets Salesforce global search find Box files, with extra set-up
Permission syncSyncs Box and Salesforce permissions from the Box Settings tab

What moves between Salesforce and Box?

Salesforcevia Box for SalesforceBox
  • Record permissions to folder access (from Salesforce to Box)
  • Extracted document data to records (from Box to Salesforce)
  • Box user activity to records (from Box to Salesforce)
Shows the data flows Box's support articles describe for Box for Salesforce (read 10 November 2026). Files stay in Box and are shown on Salesforce records.

Box supports only the most recent version of the integration. Box says syncing Salesforce permissions does not affect collaborations added by hand in Box.

How do you install Box for Salesforce?

  1. Prepare four accounts. A Box service account used only for the integration, with Box Admin or Co-admin rights; a separate Box user account on the same email domain; a Salesforce admin; and a Salesforce user.
  2. Install from AppExchange. Box recommends a sandbox, development or scratch org first. Choose Install for Admins only and approve third-party access. Box says it takes about 5 to 6 minutes.
  3. Assign permission sets. Box Admin for those who change settings, Box Standard for users, and Box Sign for e-signature users.
  4. Run Quick Setup. Connect the service account, log in as a Box user, set the root folder and assign permission sets.
  5. Finish advanced set-up. Page layouts, permission sync, your Box sub-domain if you use one, and Box Sign settings.

Users must log in with an enterprise Box account; unmanaged or external accounts are not supported. Box UI Elements in Experience Cloud use your Custom API call allocation.

Box for Salesforce or a custom Box build?

Box and Salesforce options compared
OptionWhat it coversLimits
Box for SalesforceRecord folders, file access, Box Sign, Extract, Events and searchJoint Box Enterprise and Salesforce customers; enterprise Box accounts only
Box Platform APIsFiles, metadata and webhooks for rules the package does not coverCustom code to build and maintain; OAuth, JWT or app token set-up

Most teams start with the package and add custom work only for gaps. Our Salesforce integration services cover both; to plan yours, book a discovery call. See all connector pages.

[ Architecture ]

How does Box connect to Salesforce?

How data moves between the two systems.

Box

Folders and files
↓

Box for Salesforce

Managed package from AppExchange
↓

Salesforce

Box component on record pages

[ What's included ]

What does Techila set up for Box and Salesforce?

What the integration work covers.

/01
Accounts and permission sets
The Box service account, root folder and Box Admin, Standard and Sign permission sets.
/02
Record pages
The Box component on Lead, Account, Contact, Opportunity and the custom objects you need.
/03
Permission sync
Salesforce access reflected in Box folders, planned around manual Box collaborations.
/04
Box Sign and Extract
E-signature set-up and document data written to Salesforce records.
/05
Sandbox testing
A full run in a sandbox before production, then support after launch.

[ FAQ ]

Frequently asked questions.

What architects ask before commissioning a Techila integration.

Sources

Last reviewed:

  1. Box Support, Introducing the Box for Salesforce integration (read 10 November 2026)
  2. Box Support, Installing Box for Salesforce (read 10 November 2026)
  3. Box Developer, Box Platform guides (read 10 November 2026)

Let's now look at how to build
the next 10 years of
your customer platform.

See case studies