To manage files in a shared environment, we recommend the Autodesk Vault project type rather than the legacy project types Semi-Isolated Master, Semi-Isolated Workspace, or Shared.
Individual designers who do not share files should create single-user projects.
Single-User Projects
The single-user project is the default project type. For this project type, we recommend that you make the workspace local to your computer. The project file (.ipj) is stored in the workspace.
All design files are in one workspace folder and its subfolders, except for files referenced from any number of libraries. You create and edit files in the workspace. It is not necessary to check files in and out for editing.
The file status browser is not available because you are the only person with access to the files.
Autodesk Vault Basic Projects
In Vault projects, common files are stored in a vault and are never accessed directly. The vault maintains version history and other attributes of files.
Autodesk Vault software is required to use the vault project. First install Autodesk Vault, and then create a vault project before you start working on any model files.
Vault projects have the following characteristics:
- A vault project has one workspace and one or more libraries.
- You never view or work directly on the vaulted version of a file.
- Each designer checks out files to view and edit. When checked out, the files copy to a workspace that a personal project defines. When you check edited files back in, they become available to other team members.
- You can refresh the files in your workspace to get the latest versions of files that other designers change and check in.
- Autodesk Vault maintains copies of all of the previously checked-in versions of data files. It maintains a database to store additions about edit history, file properties, and file dependencies.
- To avoid file resolution problems, projects use paths that are relative to the project file location (such as .\ or .\workspace), rather than absolute paths.
- You can set up queries on file properties, track file references, and retrieve past configurations.
- Workgroup search paths are not available. You consolidate all project folders under the single workspace search path. The workspace is the local folder mapped to the corresponding folder in the vault. The workspace can be a single folder, or can include a hierarchy of subfolders to help organize the project.
- Vault projects do not allow the use of an included path. If possible, do not use an included path, but rather use the Vault to manage files. Note: If you use it, set the Included file path option, to point to a single, read-only project file, maintained on a network by the CAD administrator. The only defined project path to include in the local project of each user file is the Workspace.
- Vault projects offer database queries, access to past configurations, and other utilities.
Legacy Projects
Semi-isolated Master, Semi-Isolated Workspace, and Shared are all legacy projects. In the Project wizard, these project types are unavailable by default. To manage multi-user projects, we recommend that you use Autodesk Vault Basic projects instead of legacy project types. If you require legacy project types, you must enable them first: click Tools tab 
Options panel Application Options General tab, and select Enable Creation of Legacy Project Types.
To avoid file resolution problems, projects use relative paths rather than absolute paths. Then paths are relative to the project file location (the workgroup for the master project; the workspace for personal projects).
After you open a file, in the browser, you can see the status of all saved files in the project, and check files in and out. After you check your edited files back in, other designers can refresh their files and see the changes.
- Semi-isolated master and semi-isolated workspace projects. In a semi-isolated environment, you store shared files on the network in a workgroup. A semi-isolated master project specifies the Workgroup for shared files and one or more libraries. Each design team member creates a personal project (Semi-Isolated Workspace) to define where to create and edit files that are checked in to the shared workgroup. In each personal project, a path to the master project is included, automatically giving access to the shared locations and libraries.
Designers check out files from the workgroup that the entire design team shares. The file automatically copies into a personal workspace (specified in the personal project) for editing.
With semi-isolated master projects, you reference components that are not in the personal workspace from the network locations.
- Shared project. Shared projects are appropriate for small design groups with well-defined tasks. A common project defines workgroup search paths and libraries. For best results, specify no other type of search path.
In a shared environment, you store shared files on the network in a workgroup that all designers access. All design team members use the same project, and check files in and out of the workgroup for editing. No workspace is defined.
Designers work on the "live" files rather than copying files to a personal workspace. File sharing requires everyone to update their assemblies to see the latest versions of files.