Summary: The benefits of working on your intranet in a sandbox environment with tips to create your own.
When working with customers in support, one of the common questions I am asked is “can I work on this within a sandbox environment?” The answer to this question is yes! Within the intranet, you can build out sub-sites and lock them down as necessary. The same principal applies to the idea of a sandbox environment.
When onboarding new intranet admins, it helps to have a place where they can play around and get familiar with the functionality. Having a sandbox environment greatly improves with this process. Some other benefits include:
Many customers love the idea of being able to work on something ‘behind the scenes’ without end users seeing the changes until they are ready for them to see them. One of the most common questions focuses on how to make changes to the home page which require sign-off from management before the change can be implemented. This is easy to do through a sandbox environment.
By creating a clone of your existing home page and moving it to your sandbox site, you can easily work on the page content behind the scenes and show it to the necessary people before pushing the home page live.
In the below example, it shows a flag icon when you hover over the ‘home page’ card on my pages screen. This indicates that you can switch this page to be your new home page. In order to push it live, you would first move the page to your home site, and then click the flag to make this your new home page.
You can build out intranet applications and add content to them in your sandbox environment prior to making these apps live for your users. Here are some ideas of what you can build out before hand:
Once you’re ready to push it live, simply move the app to a live page on your intranet where it’s new home will be located.
As you build out content behind the scenes, it is easy enough as an admin to add these links to your navigation menus. As the intranet reviews what users have access to, it will automatically hide links to any apps/pages/sites that regular users do not have access to. In the case of a sandbox idea, this works great as you can pre-populate the menus the way you want them to be with links to these locked items, and once they move to the new site, the links then update to match their new home.
With our Link interface, you have the ability to select the asset type of Site, App or Page. In selecting the appropriate asset and choosing the item from the available list, this is a quick way of creating your links in preparation for going live!
Many customers like to try out intranet design theme options prior to it being pushed live for their end users. This allows them to see how the theme changes will look on their site before it goes live. Rather than setting up a test intranet site on another server to try this out, we recommend building the theme on a sub-site. While it is not possible to migrate themes between sites on the intranet, or between the test intranet server and the production, you can try out the theme on the sub-site without having to build out a new intranet for this purpose.
Have you ever worked in a sandbox environment? Share your experiences with me in the comments section.