Box for Salesforce is available at no extra charge for joint Box Enterprise and Salesforce customers. As a Salesforce admin, you can use a Salesforce-hosted setup wizard to configure the Box for Salesforce managed package easily, quickly and correctly.
Your Box service account should serve as an account used exclusively for managing the Box for Salesforce integration; it shouldn't be assigned to an individual user. This account:
- "owns" the Salesforce content on Box,
- makes API calls from Salesforce to Box for the entire enterprise,
- and must have Box Admin or Co-admin level permissions, with Admin permissions to:
- Manage users & groups
- View/Edit users' content and Log in to users' accounts
- (as needed) Edit Sign permissions/settings for your company
- Box recommends this account have unlimited storage, as this represents the integration's storage allotment.
Log in as Box User
Next, log in as an end user, and modify your individual settings as needed.
Be sure to use your enterprise's Box account to log into the Box for Salesforce integration; Box for Salesforce does not support logging into the integration as an unmanaged or external Box account holder.
Note:
- This section is visible to all Box for Salesforce users, and allows users to control their own Box for Salesforce settings.
- All users should log in as a Box User, to fully leverage Box for Salesforce.
- This User should be different from the Service Account.
- This User should belong to the same email domain as the Service Account.
Auto-Collab
When enabled, this feature automatically adds the user as a collaborator to a record's Box folder when they view the record page. When disabled, users must manually choose to add themselves to the folder.
Enable Seamless Login
When enabled, users do not need to log into Box every time they access Box content within Salesforce. When disabled, users must log into Box any time they access Box content within Salesforce in a new browsing session.
Assign Root Folder
Set the main folder for all your Box content related to Salesforce. This is a folder at the top level of your folders hierarchy in Box. We recommend creating a new folder with a name that indicates this is the root folder, for example: Salesforce root folder, or Salesforce main folder.
Note: Your Service Account owns this Root folder. Within this folder are the individual records folders. Box for Salesforce comes with a pre-built folder hierarchy, however you can customize this to better suit your organization with custom code, or with Flows.
Assign Permissions
Configure user types, profiles, and Box access permissions. For more information on how to add permission sets in Salesforce, see here.
The supported permission sets are:
- Box Admin - for users that need administrator access to Box for Salesforce managed package, and can make changes in the integration settings,
- Box Standard - for users who will just use the integration,
- Box Sign - for users who need to use Box Sign functionality in the Box for Salesforce integration.
Advanced Setup wizard
In the Advanced Setup wizard, a user with the Box Admin permission set can:
- add the Box component to Salesforce page layouts,
- sync Salesforce permissions to Box folders,
- allow or disallow seamless login for your enterprise,
- specify the enterprise's Box sub-domain if applicable,
- customize folder mapping for converted leads,
- set up federated search,
- configure Box Sign settings
- connect a Box custom app to use UI Elements in Experience Cloud.
Add Box to Page layouts
Set up Lightning Record pages preconfigured with the Box component.
Here you can:
- configure the Lightning Record pages for Lead, Account, Contact, and Opportunity objects,
- customize their layouts, and
- add Box components and actions to other standard or custom objects and pages.
Advanced Settings
Configure settings for seamless login and content.
Here you can:
- sync Salesforce and Box permissions,
- schedule syncs,
- enable and disable seamless logins, and
- if used - specify your enterprise's Box sub-domain.
Sync Salesforce and Box Permissions
This setting enables you to use Salesforce access as a model whenever you update access to record-specific folders. This removes collaborators who gain access to record content through the integration after losing access to a given record in Salesforce.
As a User with the Box Admin settings, you can run the process by clicking Sync Now, or by scheduling a job to run.
Note:
Syncing does not affect any collaborations added manually in Box.
Seamless Login (Org-Wide)
This feature provides seamless login to Box from within Salesforce. When enabled, your Users will then see the Seamless Login setting in the Box Settings tab. They can then enable/disable seamless login for their own accounts. If individuals enable seamless login, they're prompted to log into their Box accounts once (during setup).
Seamless Login (Org-Wide) is enabled by default. If you disable it, the system prompts Box accountholders to log into Box any time they access Box content within Salesforce in a new browsing session.
Admin Delegated Authorization (Box Admin)
This feature allows users to authorize to Box, within Box for Salesforce, without their users needing to manually go through an OAuth flow. When enabled, every user in a Box enterprise and/or selected Salesforce Org will automatically be authorized. This feature works best when Seamless Login is also enabled.
Your Box Admin must enable this feature.
Box Enterprise Sub-Domain (As applicable)
If your Box enterprise uses a subdomain (for example: cloud.app.box.com instead of app.box.com), enter it in the field.
Your Box Admin can find your Box sub-domain value under Enterprise Settings -> Custom Setup in the Box Admin Console.
Mapping and Folder Customization
Automate Box folder actions in your Salesforce organization.
Convert Lead Folders
This setting moves and renames Box folders associated with Lead records to a pre-set object folder, upon lead conversion.
When a Lead folder is converted to a new object, it is automatically moved and renamed to match the new objects' naming convention, for example: Lead folder changes name to Account folder.
Hide Parent Path on Folders
This setting hides the parent folder(s) of any Box folder mapped to a record. For example, when in an ACME record:
-
When enabled, the folder path only displays ACME. If the user enters a subfolder within ACME, the folder path will display ACME > BETA
-
When disabled, the full folder path is displayed, depending on user permissions. (e.g.: All Files > Salesforce Folders > Accounts > ACME)
Template Flows
Box for Salesforce comes with pre-built Flow Templates, modifiable to fit your business needs.
Federated Search
Salesforce's global search enables you to find Box content across all Salesforce Clouds.
You can search for Box files, and search the content within Box files.
Federated searching enables you to find content within the file types identified in this article.
Box Sign Configuration
Configure Box Sign for your Salesforce objects.
Here you can:
- select for which Salesforce objects you want to enable Box Sign,
- create Box Sign buttons,
- assign Box Sign to Salesforce page layouts,
- select Box Sign email settings,
- enable or disable Box Sign automatic reminders,
- define pre-filled Salesforce tag settings,
- specify default recipients for the Salesforce object,
- select recipient roles for the Salesforce object, and
- specify signing order for the recipients of the Salesforce object.
For information on how to set up, see:
Experience Cloud Configuration
Connect your Box Custom App to add select Box UI Elements as Salesforce Lightning Components in Experience Cloud. For more information on setup, click here.
Using these Box UI elements as Lightning Components in Experience Cloud consumes your business’s Custom API call allocation.
For more information, contact salesforce@box.com.