Setting up a Local Workspace
To work with files that are under Perforce control, you will need to set up a Workspace so that the files can be managed on your local machine. You can do this via P4V by opening up the Workspaces tab in the View dropdown:
To create a new workspace, Right-click in the Workspace window and select the New Workspace option. Then enter a name for your workspace and a location where you want the files to be on your
local machine, the Workspace Root.
Once you have a server and a workspace, you will want to start adding files to it. For the moment, this needs to be done initially outside the Editor via P4V. If you already have a workspace that someone else has set up with some files already, you can skip ahead.
When you create a new project, you can choose whether it incorporates C++ code and Blueprint elements. If you are using C++ code in your project, you will see a Source/ directory as well.
You should initially add only the following directories of your project:
Folders and files highlighted in Green should be added to your depot. The Binaries folder in Yellow is optional, depending on how your team wants to work together. It is not required if every team member is going to compile their
editor/game themselves, but should be included in the initial add if any team members will just be grabbing a version from the depot to create content.
Note that the server typemap setup above should mean that coders can compile their binaries without them being set to be Read-Only by Perforce.