We're excited to announce that multi-page forms are coming soon to Box Forms.As teams build longer, more complex forms, a single-page layout can feel overwhelming to both form authors and submitters. Multi-page forms let form authors break content into logical sections, making forms easier to build and easier to complete.With multi-page forms, you can:Organize form content across multiple pages with clear titles and descriptions Add, reorder, duplicate, delete, or clear pages using page-level controls Navigate between pages during form creation with a dedicated Pages panel Enable an optional Review Step so submitters can check their answers before submittingMulti-page forms is a foundational enhancement to the Forms experience that enables authors to create more scalable, user-friendly forms today while establishing the groundwork for future capabilities that support more complex form workflows.

 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. What's newEvery 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 mattersBecause 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.

A Link Cards block can use icons in place of images. Icons keep each card compact and let you signal what a card leads to - a report, another Hub, a Hub page, a team - without sourcing and uploading artwork for every card, which is the main reason Link Cards blocks go unfinished.Select the Link Cards block and choose Icon in the block toolbar. Pick a color from the swatch next to the toggle. The color applies to every card in the block, so the block stays visually consistent. Select an individual card and use its icon menu to choose from the icon set, so each card can carry its own icon.Switching a block between Icon and Image leaves your card titles, descriptions, and links untouched, so you can try either presentation without rebuilding the block.Icons for Link Cards apply to the Box web app and require no admin configuration.

ChatGPT and Claude integrations will move from “Available” to “Added by Default” in the Admin Console. This is the same status used today for integrations like Box for Slack, Microsoft Office, Google Workspace, and Zoom, removing the extra step of manually adding the integration before it can be used. Concurrently, the specific Ask ChatGPT and Ask Claude actions in Box file previews will also be enabled by default, allowing users to seamlessly access these preview actions without prior manual installation. What’s changingIf Claude and/or ChatGPT are currently set to Available, they will move to Added by Default. Users will see Ask ChatGPT / Ask Claude in the Preview sidebar without first installing the integration. Clicking the action takes the user to Claude or ChatGPT with the Box file ID and a file-type-specific sample prompt. Users still need to authenticate with their own Claude or ChatGPT account before they can use the action. Customers already using these integrations will automatically receive the new file-type-specific prompts; no reinstall is required. What’s not changingIf an admin has disabled or blocked Claude or ChatGPT, either individually or through the global integrations setting, that configuration will continue to be respected. Admins remain in full control and can disable either integration at any time under Admin Console > Integrations. What if I'd prefer to keep things as they are?You're always in full control. Admins can disable Claude or ChatGPT individually at any time from Admin Console > Integrations — that control isn't affected by this change. If you'd like to opt out before the rollout date, you can make that change any time before September 8, 2026.When does this take effect? This change goes live on September 8, 2026. How to Opt OutTo disable a specific action: Admins can turn off Ask ChatGPT or Ask Claude individually by clicking Configure on the integration in Admin Console > Integrations and toggling each file-type action off. To opt out of Added by Default: Admins need to disable the integration completely, which removes user access rather than just the default status.Effective date: September 8, 2026