Periodic replication of Sandbox environment with Production settings/folder structure
As we become more complex with usage of Box, we maintain Sandbox environments and are using it to test Governance Policies, integrations, and more.
Other SaaS providers (e.g., Workday) will push a replication of Configuration Settings (with an option for the customer to not replicate) from the Production to Sandbox environment. This helps keep the two in sync.
It would also be enormously beneficial if the folder structure and dummy users (not content) could be replicated into the sandbox environment for a better sense of how changes will affect Production.
We are planning to bring gradually mirroring of Production/Parent EID setting, content and metadata templates to Sandboxes. This is planned as a incremental development across FY27 and FY28.
-
AdminAnonymous
(Admin, Box)
commented
We have enabled in May capability to copy content from the production Enterprise into Sandbox via Admin Console > Platform > Sandbox. This is purely to copy files and folders, excluding associated metadata / metadata templates. (see screenshot enclosed)
We are working to include metadata during above copy process - the goal is to release it September/October.
There is no plan to include automatic/periodic replication of Production into Sandbox, as this would overlap with backup capability. Content and metadata replication between Enterprise account and Sandbox will remain manual, admin triggered process.
-
Sean Bronee
commented
As access and user maintenance are the most critical aspects of our configuration, it would make most sense to us to allow users to be replicated (i.e. not dummy), in sand and prod, so that changes to the configuration can be tested with end-users using real-life access scenarios (such as logging with SSO, or logging in as external), or being parts of groups that are synced with the AD. Note that we don't need all users replicated (especially not externals) necessarily, but need to be able to invite some users on both environments so they can login in a similar way on both environments using their real email and credentials