Thanks to Hiren and
Modernizing Permissions for an AI-Powered World
How can teams keep sensitive work secure without making folder structures harder to manage? As organizations adopt AI and streamline work across teams, permissioning needs to keep pace.
Demo: breaking permission inheritance
Today, access granted to a folder generally flows down through its hierarchy. The concept demo showed how an owner or co-owner could disable that inheritance on a specific folder, then manage access there separately.
The example focused on a financial services team working across public markets and private investments. A sensitive, active M&A deal could be isolated within a shared structure so that only the appropriate people retained access. The goal is to support cleaner folder structures while keeping access appropriately limited.
Owners and co-owners would control the setting and retain visibility into the full hierarchy. The team also discussed designing the experience to help admins understand current access and make changes efficiently, including through bulk actions.
Customer Q&A
Customers raised several practical questions and considerations:
-
Will owners and co-owners control the setting? That is the current direction. Owners and co-owners would be able to toggle it and would continue to see the full hierarchy.
-
How will admins understand who has access? Reporting is a key focus. The team said it would review existing collaboration and folder reports and consider whether new reporting is needed.
-
Will collaborators know when inheritance is disabled? The discussion highlighted the need for clear, understandable experiences and actionable error messages that help people resolve access issues without exposing sensitive information.
-
Will the Collaboration APIs support disabling inheritance at the start of rollout? This question was raised in chat. The team did not confirm availability at initial rollout. API and integration requirements are part of the design partner work, with compatibility and security reviews planned before general availability.
-
How does this affect Box AI agents? Agents work within the user’s access context, so they can access content the user can access. The team said this capability does not add separate agent controls; additional AI-specific guardrails are being addressed by the security team.
-
What’s the expected timing? The team described the work as early. The design partner program was starting, with a private beta hoped for by the end of Q4 and a tentative broader-release target of late spring or early summer. These are estimates and may change.
-
Will customers receive training materials? The team expects to provide FAQs, walkthroughs, videos, use-case examples, and best-practice guidance as the feature progresses.
-
Customers also shared how disabling inheritance could help simplify folder structures, support gradual onboarding into specific departments, and keep sensitive work within standard team folders.
The discussion also surfaced the importance of understandable error messages, admin enablement, and security review across Box products and integrations.
Box is currently seeking customer input through its design partner program; please reply here to share use cases or ask about participating in the program!