You should be familiar with project areas, configuration spaces, snapshots, workspaces, and change sets, which are described in Management of shared design resources.
You must be logged in to a Design Management project, and the project must contain a snapshot, which is a view of the project at a specific point in time.
Each project area, also called a project, is associated with a configuration space, or space, which in turn contains a default workspace. This default workspace can contain multiple snapshots and workspaces. A project area can also contain multiple workspaces. For example, in a banking project area, you might have a workspace for the resources that define the application logic, a workspace for the resources that contain the database logic, and a workspace for the resources that compose the user interface.
Because workspaces are editable, to ensure consistency of versions in workspaces, you should create workspaces only as children of snapshots; do not create workspaces that are direct children of other workspaces.
Multiple workspaces can contain a copy of the same resource. Changing a resource in your workspace does not affect the same version of that resource in other workspaces until other team members choose to accept your changes into their workspace by using the Accept Incoming Changes operation. For more information about that operation, see the related topic link at the end of this topic.
If you do not create a change set, you can switch the context to the workspace that you created. Each time that you save changes to a resource, a change set is created automatically.