Switching between Fuuz Environments Build QA Production

Switching between Fuuz Environments (Build, QA, Production)

This article demonstrates moving between a Build and QA environment. Keep in mind that you must have access to these different environments in order to perform this action. If you do not, you'll need to get with your system administrator to set you up first.

🎥 Video walkthrough: Watch on Vimeo

In addition, Roles and Apps are not guaranteed to be the same between environments — this depends on how your system has been configured thus far. So don't worry if you switch between Build and QA and something isn't there; this just means that something was not yet configured in QA, for example. Work with your team to get the Apps installed in QA or Production.

Often, things behave differently in Build and QA environments than they do in Production. Why is this? Because Build and QA are sandbox environments: sometimes your developers have made changes to the apps you use in order to check out some new feature or function, and sometimes (often) the data is not the same. Data does not automatically replicate itself across these environments. Not all users will have access to all environments — this is determined by your Enterprise Administrator.

With Fuuz, you do not have to create your own Build, QA, and Production infrastructure — this is an out-of-the-box feature. Fuuz also handles all the support, maintenance, and monitoring of these environments for you.

Note: Build/QA environments do not come with the SLA that a production environment does.

For additional support, please submit a support ticket.

See Also

• Switching-my-active-Role-within-Fuuz
• Setting-up-In-House-Fuuz
• Sharing-A-Page
• Trouble-Logging-Into-Fuuz

---

Source: support.fuuz.com