Box Integrations Updates & Release Notes

What's new

We're excited to introduce a new layer of security controls for the Box MCP Server. Box admins can now control which Box MCP Server tools each unpublished platform app is allowed to use. For every app—regardless of authentication method—admins can apply the organization-wide MCP policy or create a custom set of permitted tools specifically for that app. This gives organizations the same granular governance for their internal, custom-built apps that was previously available only for published integrations.

Every platform app listed in Admin Console > Platform > Platform Apps now includes its own Box MCP Server tab. From there, admins can define exactly which tools that specific app is allowed to use, independently of the organization-wide global controls.

To find it: go to Admin Console > Platform > Platform Apps, locate the app by name, click to open it, and select the Box MCP Server tab.

Admins can now:

• Choose between Global and Custom configuration for each unpublished platform app. Global inherits the organization's global MCP settings; Custom lets you define a set of tools scoped to that app alone.
• Enable or disable individual tools within a Custom configuration, grouped by category — such as Files and Folders, Search, or Collaboration.
• Grant a trusted internal app broader or different access than the global default without affecting any other app.
• Revert to the organization's global policy at any time by switching from Custom back to Global.

Why it matters

Because unpublished apps are typically internal or custom-built and haven’t undergone Box’s app-publishing review, admins need more granular control over what each app can access. These controls help enforce least-privilege access by ensuring each app can call only the tools it genuinely needs. They also give admins one consistent way to govern both published and unpublished MCP-connected apps across their organization.

We’ve released a new version of Box for Salesforce, now available for the download at the Salesforce AppExchange.

This release focuses on bug fixes and improvements to enhance the integration, including:

Box for Salesforce

Box Sign

• Improved Box Sign status sync consistency.
• Enhanced the Box Sign webhook to automatically retry when the Box Sign API status is behind the triggering event.
• Fixed an issue causing failed updates to appear as delivered skipping retry.
• Fixed an issue where the Box Sign scheduled sync reprocessed already-completed sign requests due to a truncated signer email value, causing repeated sync failures.
• Fixed an issue where a contact's phone number was not auto-populated when requesting SMS authentication for a sign request.
• Added a Box Sign Sync section to the Box Sign Configuration page in Box Settings, with a link to Using Box Sign Sync in Salesforce to help admins configure it correctly to receive real-time updates from Box Sign.

Box Doc Gen

• Fixed an issue where the Custom Object for Contact Details did not resolve correctly in Box Doc Gen templates.
• Fixed an issue where uploading a template in the Doc Gen Template Manager failed to collaborate the creating user on the new template folder.
• Fixed an issue where Box Doc Gen failed due to fields not present in the Salesforce API version.
• Added support for using lookups in Box Doc Gen name tags.

General

• Fixed an issue where collaborations on linked folders were removed or not added for the users.
• Added support for automatic collaboration in Box UI Elements when a Salesforce record ID is provided as input.
  • Note: Auto-collaboration does not apply when a hardcoded file or folder ID is used.
• Improvements to validation messaging during Box for Salesforce setup.

.. and other minor improvements and enhancements to the integration related to error messaging and usability.

For additional information, please refer to Box Support and Box for Salesforce documentation.

What's New

Box Utility

The latest version of the Box for Salesforce package is now available on Salesforce AppExchange. This release introduces new capabilities for Box Utility and Box Sign Templates, along with improvements across Box for Salesforce features.

Box Utility is now available in additional Salesforce Lightning apps, providing users with quick access to Box functionality directly from the Salesforce utility bar.

With Box Utility, users can access Box capabilities without leaving their current Salesforce workflow. The utility automatically detects the Salesforce record context, helping ensure that Box content remains associated with the correct record as users navigate.

This release introduces Box Notes support within Box Utility, allowing users to:

• Create, edit, and delete Box Notes directly from Salesforce.
• Create record-level notes associated with Salesforce records.
• Access personal Box Notes from their Salesforce workspace.
• Associate personal notes with Salesforce records when needed.

Box Notes are stored as Box Note files, allowing users to benefit from Box collaboration and version history while continuing to work within Salesforce. Learn more: Using Box Utility in Salesforce, Setting up Box Utility in Salesforce

Box Sign Templates

Box Sign Templates are now available in Box for Salesforce, enabling organizations to standardize and simplify recurring signature workflows.

Salesforce admins can import Box Sign Templates into Salesforce and configure reusable signing experiences for common business processes such as contracts, NDAs, onboarding documents, and approval workflows.

When sending a signature request, users can now select an imported Box Sign Template instead of manually configuring each request.

Box Sign Templates support:

• Predefined documents included in the template.
• Configured recipients and signing order.
• Template-based email subject and message settings.
• Placeholder recipients that can be completed when sending a request.
• Configurable Salesforce field mappings to reduce manual data entry.

Template-based signature requests are tracked in Salesforce the same way as standard Box Sign requests. Learn more: Using Box Sign Templates in Box for Salesforce, Using Box Sign in Salesforce

Bug Fixes & Improvements

1. Fixed an issue where some Salesforce records were not correctly associated with their Box folders due to incorrect folder ID values being stored.
2. Improved Box Doc Gen reliability when using dynamic file naming. Previously, generating documents with tags used in both the document content and file naming configuration could cause generation failures.
3. Added support for specifying the generated file name in Box Doc Gen automation, giving administrators more control over how generated documents are named and stored.
4. Improved folder collaboration on UI Elements behavior by continuing to automatically collaborate users on Salesforce record folders while removing unnecessary automatic collaboration for manually specified Box folders.
5. Fixed an issue where Box Doc Gen could fail when using fields from related Salesforce records.
6. Improved Box Sign Sync by notifying users when a sync fails, providing better visibility into Box Sign synchronization issues.

For questions or issues:

• Visit the Box Community
• Contact Box Support
• Review the Box for Salesforce documentation

The new Box for Agentforce managed package is now available on Salesforce AgentExchange. This release introduces new capabilities that enable organizations to bring Box content management, Box AI, and document workflows directly into Agentforce.

What's New

Box User Agent & Agent Topics

Box for Agentforce now includes the packaged Box User Agent (Box_User_Agent_v1_Template), an Agentforce employee agent designed to help users work with Box content directly from Salesforce.

The Box User Agent includes preconfigured Box capabilities for managing Box files, folders, and permissions, as well as using Box AI to analyze and interact with content.

The packaged agent includes the following Agent Topics:

• Box AI – Ask questions about files, generate text, and extract information from documents using Box AI.
• Manage Box Folders – Create and manage Box folders associated with Salesforce records. Retrieve folder IDs, access folder URLs, and create record-specific Box folders to help users quickly organize and access Salesforce-related content.
• Box Doc Gen & Sign – Generate documents from Box templates using Salesforce data and optionally send documents for signature using Box Sign.
• Box Content Sharing & Collaboration – Manage access to Box content through collaborations and shared links.

The Box User Agent helps organizations quickly deploy Box-powered Agentforce experiences without manually configuring individual Box actions and topics. Learn more: Using the Box User Agent and Agent Topics in Box for Agentforce.

Box File Selection

Box for Agentforce now includes the Box File Selection Lightning Type, enabling users to select Box files directly within Agentforce actions.

Instead of manually entering Box file IDs, users can choose files using the integrated Box file picker from:

• Recent Items – Select from recently accessed Box files.
• Browse Box Files – Browse and select files using the Box Content Picker.
• Current Record Folder – Select files from the Box folder associated with the Salesforce record context.

The selected file is automatically passed to the Agentforce action, making it easier for users to interact with Box content during AI-powered workflows.

The Box File Selection capability is used by Box AI actions that work with individual files, including:

• Ask questions about a file.
• Generate text from a file.
• Extract fields from a file.
• Extract metadata from a file.

Note: To use Box File Selection, users must be assigned the Box Agentforce permission set by a Salesforce administrator.

Salesforce administrators and developers can also use the Box File Selection Lightning Type in their own custom Agentforce actions. Learn more: Installing Box for Agentforce.

Support

For questions or issues:

• Visit the Box Community
• Contact Box Support
• Review the Box for Agentforce documentation

The new Box for Agentforce managed package is now available on Salesforce AgentExchange. This release introduces new capabilities that enable organizations to bring Box content management, Box AI, and document workflows directly into Agentforce.

What's New

Box User Agent & Agent Topics

Box for Agentforce now includes the packaged Box User Agent (Box_User_Agent_v1_Template), an Agentforce employee agent designed to help users work with Box content directly from Salesforce.

The Box User Agent includes preconfigured Box capabilities for managing Box files, folders, and permissions, as well as using Box AI to analyze and interact with content.

The packaged agent includes the following Agent Topics:

• Box AI – Ask questions about files, generate text, and extract information from documents using Box AI.
• Manage Box Folders – Create and manage Box folders associated with Salesforce records. Retrieve folder IDs, access folder URLs, and create record-specific Box folders to help users quickly organize and access Salesforce-related content.
• Box Doc Gen & Sign – Generate documents from Box templates using Salesforce data and optionally send documents for signature using Box Sign.
• Box Content Sharing & Collaboration – Manage access to Box content through collaborations and shared links.

The Box User Agent helps organizations quickly deploy Box-powered Agentforce experiences without manually configuring individual Box actions and topics. Learn more: Using the Box User Agent and Agent Topics in Box for Agentforce.

Box File Selection

Box for Agentforce now includes the Box File Selection Lightning Type, enabling users to select Box files directly within Agentforce actions.

Instead of manually entering Box file IDs, users can choose files using the integrated Box file picker from:

• Recent Items – Select from recently accessed Box files.
• Browse Box Files – Browse and select files using the Box Content Picker.
• Current Record Folder – Select files from the Box folder associated with the Salesforce record context.

The selected file is automatically passed to the Agentforce action, making it easier for users to interact with Box content during AI-powered workflows.

The Box File Selection capability is used by Box AI actions that work with individual files, including:

• Ask questions about a file.
• Generate text from a file.
• Extract fields from a file.
• Extract metadata from a file.

Note: To use Box File Selection, users must be assigned the Box Agentforce permission set by a Salesforce administrator.

Salesforce administrators and developers can also use the Box File Selection Lightning Type in their own custom Agentforce actions. Learn more: Installing Box for Agentforce.

Support

For questions or issues:

• Visit the Box Community
• Contact Box Support
• Review the Box for Agentforce documentation

We’ve released a new version of Box for Salesforce, now available for the
download at the Salesforce AppExchange.

This release focuses on bug fixes and improvements to enhance the integration, including:

Box for Salesforce

• Fixed an issue in the Box Doc Gen record page where searching after selecting a file could result in an unexpected error
• Fixed an issue affecting automatic user collaborator provisioning for first-time Experience Cloud users
• Fixed an issue where the Open Document button in Box Doc Gen directed users to an incorrect Box URL after document generation
• Added support for downloading files from the prebuilt Box Components in Salesforce
• Enhanced the Seamless Login feature by allowing users to disable it for Login As sessions. Added a user setting in Box Settings that enables admins to allow Seamless Login for impersonated user sessions (this setting is disabled by default).

For additional information, please refer to Box Support and Box for Salesforce documentation.

We’ve released a new version of Box Agent for ServiceNow, now available for the download at the ServiceNow Store.

Enhancements

Added Support for Box Classification Labels

Box Agent for ServiceNow now supports Box Classification Labels when accessing files through agent workflows via ServiceNow NowAssist.

When a user prompt references a Box file with a classification label applied, the agent will:

• Detect the presence of a classification label at the file level.
• Inform the user that the content has a classification label and may contain sensitive information.
• Prompt the user for confirmation before proceeding with any agent action.
• Proceed only after the user explicitly confirms that they want to continue.

This behavior applies to both Content Insights and Data Extraction workflows. Learn more about Box classification labels here.

Added Folder Search and File Listing Capabilities

Box Agent for ServiceNow now supports folder search and file discovery capabilities, enabling users to find and explore Box files directly through natural language prompts.

The agent can now:

• List all files within a specified Box folder.
• List all folders accessible to the user.
• List all files accessible to the user across their Box account.

To learn more about Box Agent for ServiceNow, refer to the support documentation here.

We’ve released a new version of Box for Salesforce, now available for the download at the Salesforce AppExchange.

This release focuses on bug fixes and minor improvements to enhance the integration, including:

• Fixed an issue that could cause Box Doc Gen document generation to fail with an “uncaught error” message when generating documents from Salesforce records
• Fixed an issue affecting redirect URL configuration in the Box Settings permission set
• Added a warning message for Seamless Login feature to provide users with additional context during configuration
• Fixed UI indentation for Box Quick Links lightning component
• Upgraded Search invocable by adding trash and scope_content attributes
• General stability, translation, and performance improvements

For additional information, refer to Box Support and Box for Salesforce documentation.

What's New

Additional Sign Recipient Verification Methods

Box Sign in Salesforce now supports Additional Recipient Verification methods, providing enhanced flexibility for securing signature workflows.

Recipients can now be configured with the following verification methods when sending signature requests from Salesforce (optional):

• SMS Authentication – Sends a one-time passcode to the recipient’s mobile device, which must be entered to verify identity before accessing the document.
• Box Login – Requires recipients to authenticate using a Box account before accessing the signature request. Available only on the Enterprise Plus and Enterprise Advanced plans.
• CAC/PIV Authentication – Supports Common Access Card (CAC) or Personal Identity Verification (PIV) smart card authentication for U.S. federal employees and contractors. This capability requires the CAC/PIV add-on.

This enhancement enables stronger identity verification controls for sensitive and regulated signing workflows, including support for per-recipient configuration.

Learn more:
Additional Recipient Authentication, Using Box Sign in Salesforce, Box Sign for Salesforce - FAQ

Box Quick Links Widget

The Box Quick Links widget is now available in Salesforce as a Lightning Web Component (LWC) that enables users to generate and copy Box links directly within Salesforce.

The widget supports generating the following link types:

• Shared link for the record’s Box folder
• Shared links for selected files within the folder
• File Request links for uploading files directly into Box

This capability enables users to quickly generate, access and use Box shared links directly within Salesforce workflows.

Learn more:
Using Box Quick Links widget

Bug Fixes & Improvements

Box for Salesforce

• Fixed an issue preventing Salesforce Service Account re-authentication due to redirect behavior.
• Resolved an issue with sender/recipient data display in Box Sign when sending multiple requests in the same session.
• Improved Box Doc Gen template access handling by automatically adding Salesforce users as collaborators when required template permissions are missing.
• Fixed an issue causing errors when downloading JSON files for existing Box Doc Gen templates, which resulted in a null reference error.
• Improved translations across the Box for Salesforce managed package for better consistency across supported languages.

Support

For questions or issues:

• Visit the Box Community
• Contact Box Support
• Review the Box for Salesforce documentation