{Project} uses the concept of Content Views to create snapshots of a set of repositories and make them available to hosts registered to it. For example, if you want a group of hosts to have access to a specific version of a set of repositories, add those repositories to a Content View, publish and promote to a lifecycle environment. You can then register hosts to this Content View. These hosts have access only to repositories at the version specified in the Content View. This means that you can continue to update repositories on your server while your hosts still consume only the versions of the repositories that they are registered to. If you do not use Content Views and lifecycle environments, all your hosts consume content from the Default Content View and Library environment, which is a snapshot of the latest version of the content on your server. For more information about content management using Content Views and application lifecycles, see: