Set Kitchen Type¶
Minimize the cost for analytic team members to experiment by giving them isolated and disposable workspaces that reflect their production environment. Best practice during kitchen creation is to outline whether a kitchen—or child kitchen—is permanent (i.e. static) or temporary (i.e. a sandbox).
Use the Description field on the Configure Kitchen page to indicate to users whether a kitchen is static or a sandbox.
Assign kitchen type with kitchen roles¶
With the kitchen roles feature activated, all kitchens are created as sandbox kitchens, meaning that they are considered temporary, development workspaces. With the kitchen type feature, authorized users can change a kitchen from a sandbox environment to a static environment.
Note
The required permission to change kitchen types is Set kitchen type. By default, this is assigned to Super Users only.
Change a sandbox kitchen to a static kitchen¶
- Navigate to the Configure Kitchen page.
- From the Kitchens page, click Configure Kitchen next to a kitchen name.
- From the Recipes page, click Configure Kitchen next to the kitchen name in the green navigation bar.
- Select the Advanced tab.
- Check the Static Kitchen box.
- Click Update to save your change.
The system now verifies kitchen role permissions when a user wants to perform advanced actions, such as deleting the kitchen or updating recipes.
Warning
Sandbox/Static access configured for all roles: All kitchen roles are defined with permissions for both sandbox kitchen access and static kitchen access. If a static kitchen is returned to a sandbox type, the original sandbox access is activated.