We're excited to announce four new block types now available in Box Apps. These additions give builders more powerful, flexible ways to design interactive, self-service app experiences and give app users faster access to the tools they need, right where they work.
New Block Type: Page Filter
App builders are now able to add a Page Filter block to the top of an App page, enabling app users to filter the content displayed across the entire page based on metadata values without editing the App. This turns any App page into an interactive, filterable dashboard.
How it works
Builders add a Page Filter block to the top of an App page. The block automatically populates all metadata templates used on that page, so builders don't need to manually select templates. Builders then configure which filters are available to users in view mode. When a user applies a filter, only the blocks on the page that use the filtered metadata field are affected while other blocks remain unchanged.
Key details
- Auto-populated templates: The Page Filter block automatically detects all metadata templates in use on the page, eliminating guesswork for builders.
- Multi-template support: If multiple metadata templates are used on a page, users can see which template each filter belongs to via a tooltip on hover.
- Filter reordering: Builders can reorder filters via actions menu in the config sidebar.
- Non-permanent filters: Applied filters are session-based, so they reset on page refresh or when the tab is closed. Users can also reset filters manually via a Reset button.
- Conflict handling for overlapping filters: For Date and Number fields, when a page filter overlaps with a block's own filter on the same field, builders can configure the behavior as either Replace (the page filter value replaces the block's filter) or Narrow (both filters apply together, showing only the intersection).
- Up to 10 filters: Page Filter supports up to 10 filters per page.
Why it matters
Modern App pages often surface content across multiple metadata templates and workflows. The Page Filter block gives end users the ability to slice and explore that content on their own without needing builder access or creating separate Views. It's the foundation for building truly interactive, dashboard-style App experiences.
New Block Type: Button
App builders are now able to add a Button to the App sections, giving users one-click access to the most commonly used tools during app collaboration.
How it works
Builders add a Button block to the App sections and configure an action. In the initial release, supported actions include Form and Shortcut. When a user clicks the button in view mode, the configured action is triggered immediately.
Key details
- Supported actions (initial release):
- Form: Opens a form submission modal on button click.
- Shortcut: Redirects the user to a configured URL on button click.
- Placed in the App section: Buttons appear at the top of the App page section for easy, always-visible access.
Why it matters
The Button turns the App sections into a true command center. Instead of navigating away to submit a form or jump to a related resource, users can do it all in one click.
New Block Type: Sign Template
App builders are now able to pin a Box Sign template directly on an App page. In view mode, clicking the block opens the selected Sign template in context, giving users a fast, in-app entry point to kick off a signing workflow without ever leaving the App experience.
How it works
Builders add a Sign Template block from the block picker and select a Sign template from their available templates, which are searchable by name. The block displays the template name and Box Sign icon in both edit and view mode. When a user clicks the block, the Sign template opens on the same page, following the same experience as initiating a template from the Box Sign tab.
Key details
- In-context signing: Users can initiate a signing workflow directly from an App page, no need to navigate to the Sign tab separately.
- Searchable template list: Builders can search available Sign templates by name when configuring the block.
Why it matters
Signing workflows are a critical part of many business processes. By embedding Sign templates directly into App pages, teams can reduce friction and keep users focused.
New Block Type: Uploader
App builders are now able to add an Uploader block to any section of an App page, configured to point at a specific Box folder. Users can upload files directly from within the App.
How it works
Builders add an Uploader block and configure it by selecting a destination Box folder. In view mode, clicking the block opens a file upload modal where users can drag and drop or select files. Uploaded files are sent directly to the configured folder. Users never see or choose the destination; they simply upload.
Key details
- Flexible placement: The Uploader block can be added to any section of an App page.
- Folder-targeted uploads: Builders configure a single destination folder; users upload without needing to know where files are going.
- Permission-aware: Only folders the builder has access to are selectable at configuration time. If the builder's access to the configured folder is later revoked, the block surfaces a clear error state in view mode. Upload behavior at runtime respects the uploader's own Box permissions on the destination folder.
- No folder browsing for viewers: App users in view mode can only upload. They cannot browse or view existing contents of the destination folder.
Why it matters
Collecting files from collaborators is a common workflow need. The Uploader block eliminates the friction of leaving an App to find the right folder and upload manually.
Availability
All four new block types are now available in Box Apps.