I recommend following this guide rather than mines:
My Setup uses the Unreal Engine Stream for the workspaces and the guide from Perforce is using the Project Stream for the Workspaces which I find is better for also managing Dev and Release Streams.
I think having a look at my settings can be helpful though, since the tutorials from Perforce don’t go much into depth when it comes to these topics.
<aside> 💡 If you aren’t planning on modifying the Unreal Engine and you don’t have much experience with Perforce, I would suggest to not use UnrealGameSync. You can go back later to UnrealGameSync if you want to start modifying the Unreal Engine.
</aside>
This Guide will contain the steps to setup a Perforce Server for UnrealGameSync. I won’t go into details and explain what has been already well explained in other Guides / Documentations. Have a look at the Ressources if something is unclear.
To get started with Unreal Game Sync with no costs involved and to save up drive space to utilize as much from free licenses as we can. We also want to achieve that one Developer only needs one Workspace. The free License from Perforce allows for 5 users and 20 Workspaces. With potential Automation pipelines occupying Workspaces too, you want to save up on Workspaces if you want to continue using the Free License.
The structure is inspired by this talk Source Control & Remote Team Collaboration | Unreal Fest 2022: