As an Admin, when you connect a production org with sandboxes to Hutte, the platform will fetch all available sandboxes for you. You also have the option to create a sandbox directly through Hutte.

You can also add them to a Pool, ensuring that unused Orgs are kept refreshed automatically or easily refreshed manually.

You can choose a fresh Org close to the source of truth – possibly the production org – or even a different one.

When it comes to making changes, you can seamlessly connect from VS Code using our “auth snippet.” Hutte allows you to preview what has changed (identifying metadata in a dirty state), and it will ‘pull’ those changes – essentially transferring them to Git.

You can also create a pull request for your changes in the connected Git repository.

On the Pool list view, you'll find all Orgs that have been made available for the Pool. The ones currently in use are marked as "In Use" and cannot be claimed for feature development. They are also excluded from being refreshed. The other Orgs will display the "Eligible for refresh" status if they have passed the 24-hour window required by Salesforce.

If an Org hasn't reached that window, it is considered fresh and ready to use. You can effortlessly refresh all Orgs with a simple click of a button.

You can also enable a scheduler to ensure that all Orgs in the Pool not currently in use undergo automatic refreshes. These refreshes happen every hour, refreshing all eligible Orgs. You can also configure the scheduler to avoid refreshing during specific time frames.

As a user, you'll have an overview of all available Orgs when selecting "Pool," ordered by their last refresh date. You can easily select a fresh Org from this list and start your feature development.

Once you have finished your work, pulled your changes, and marked your feature as complete, the Org will be automatically returned to the Pool and refreshed for future feature development.