<aside>

The first tab under your Project Settings contains several settings which affect the whole project. You’ll see slightly different options here for Scratch Org projects vs. Sandbox projects.

</aside>

Project name

<aside>

Here, you can rename your project by typing the new name into the text field and clicking “Save”.

</aside>

Default duration of Scratch Orgs created manually (Scratch Org projects only)

<aside>

The number entered here will dictate the number of days that a manually-created Scratch Org will last when you click the “New Scratch Org” button on your main project dashboard.

</aside>

Base Git branch

<aside>

Here you can specify the Git branch that contains the source code that will be pushed to this Scratch Org. Usually this will be “Main”, but sometimes you’ll want to specify a different branch.

</aside>

Path to SFDX Project

<aside>

If your SFDX project is not located in the root directory of your connected Git repository, you’ll need to enter the path to your project in this field, specifically the directory where your sfdx-project.json lives.

</aside>

Salesforce CLI (sf) version

<aside>

Here you can see the Salesforce CLI (sf) version that is used for executing any code defined in your hutte.yml. We recommend to use the default option, “latest”.

</aside>

Allow parallel features (Sandbox projects only)

<aside>

Enable this option to allow the creation of multiple features simultaneously within a single Sandbox. Keep in mind that when multiple features are active concurrently, it becomes challenging to discern which specific metadata changes pertain to each individual feature.

This control doesn’t apply to Pool Orgs, since they are designed to be short living

</aside>

Scratch Org configuration file (Scratch Org projects only)

<aside>

Here, you’ll find a code field that contains your Scratch Org’s default configuration file.

</aside>

<aside>

</aside>

<aside>

You can change the “shape” of your Scratch Orgs by editing this file. If you're already using an SFDX project, you'd likely copy the content of your config/project-scratch-def.json there. You can use *{current_user}* for adminEmail and *{org_name}* for orgName to dynamically set those values for every Scratch Org created from Hutte.

If you would like to mimic the shape of a production environment or a developer edition, we suggest to make yourself familiar with Salesforce’s Org Shape capabilities, which are perfectly supported by Hutte.

</aside>

Packaging Flags

<aside>

Here you can toggle two options on and off. They are both set to “Off” by default.

</aside>

<aside>

1. No ancestors
   1. Toggling this “On” will exclude second-generation managed package (2GP) ancestors in Scratch Orgs you create in this project. </aside>

<aside>

1. No namespace
   1. Toggling this “On” will cause Scratch Orgs created in this project to have no namespace, even if the Dev Hub has a namespace. </aside>