Toggle is a feature that allows the owner of a world to hide sections and content from viewers. If the toggle is turned off, the hidden content will appear on screen again when clicked. This is similar to the visibility settings in Facebook. The toggle is applied at the global level, and will affect all versions of a world that are published to the web or in mobile apps. Note that spoilers and dynamic content that load after the page is loaded can break visibility toggles.

During runtime your tool will query an outside data source or service such as Kameleoon to read the configuration of your feature toggle. If the toggle is flipped to ON, your tool will execute the function it has been configured to do. If the toggle is flipped to OFF, your tool will not execute the function. This configuration can be changed at any time without code deployment.

Many teams use a release toggle to test new features in production. The goal of this type of toggle is to enable the team to test new features in a live environment while still being able to roll back to an old version in case there are problems. This practice is also known as blue-green deployment. Release toggles should generally only be in place for a short amount of time, and the team should be proactive in adding tasks to remove them once they are no longer needed. This is because a code base filled with toggles will have a higher maintenance burden. Savvy teams consider this inventory as having a carrying cost and seek to keep it low.