does allow your project teams to access project servers regardless of the WAN
status.
Using a single vault for all projects does, however, have a downside. Because
you can assign user permissions on a per-vault basis only, you have less
flexibility to manage user access control. As a result, if you have users that
need edit permission for one project, they are automatically assigned edit
permission for all the projects in that vault. In Vault for Civil 3D 2008, each
project can have unique access control per project folder. For example, the
Alignments folder in the Source Drawings folder of the <Project> can have
read-only access for the Drafting group, and edit permissions for the Design
group, and so on.
Folder Permissions—This approach works well if you have several departments
within your organization that use Civil 3D. Each department—such as your
survey, site, or highway departments—gets its permissions according to project
folders. This allows you to manage departmental permissions and access to
projects separately. For example, you can assign write access to your surveyors
to only their folders within the project, while providing site and highway
teams with read-only access that allows them to consume (use, copy, display)
but not edit survey data.
Multiple Vaults
: In some cases, it may be advantageous to partition your data
into multiple vaults on the same server. For example, you may choose to keep
projects organized by year, in which case you would create a vault for every
year. Thus, you could have several office locations with their own Autodesk
Vault to log onto, using the following hierarchy: Location \ Year \ Project.
For example, a project named “J06068” could reside in the “2006” folder that
is in the “Jackson” folder. In other words, the folder structure would be:
\Jackson\2006\J06068.
Description
Folder level
This denotes the location where the Vault server resides.
\ Jackson
This denotes the year of the project.
\ 2006
This denotes the name of the project, and includes a meaningful
prefix. In this example, the project name uses a “J” prefix to indic-
\ J06068
ate the office that originated the project—in this example “Jack-
son.”
Organizing Your Projects | 99
Summary of Contents for 23703-010008-1600A - Civil 3D 2006 Essentials
Page 1: ...AutoCAD Civil 3D 2008 Moving from Land Desktop to Civil 3D April 2007 23705 010000 5011A ...
Page 4: ...1 2 3 4 5 6 7 8 9 10 ...
Page 8: ...viii ...
Page 86: ...78 ...
Page 130: ...122 ...
Page 132: ...124 ...