| Description | Enter a description of the purpose for this development. |
| DesignSync Server | Click  to search for and select the DesignSync server. |
| Development Path | Enter the directory path to the development. You can only edit this value if the development instance is in the Created state. |
| Development Area Root | Enter the path to the development area. If you change this path, the path for development areas that already exist is not change. Subsequently-created development areas will use the new path. |
| UNIX Group | Enter the UNIX group that provides group ownership for the development file hierarchy on the server. |
| Allow Area Path Override | Select whether to allow the user to override the development area path:| Option | Description |
|---|
| Yes | Users can specify their own path name for their development area. | | No | Users must use the development area root path. | | Default | The value for the development associated with this instance is used. |
|
| Allow External Areas | Select whether to allow the user to use a development area path on clients that do not have direct access to the main project path:| Option | Description |
|---|
| Yes | Users can create development areas on clients that do not have direct access to the main project path. | | No | Users cannot create development areas on clients that do not have direct access to the main project path. | | Default | The value for the development associated with this instance is used. |
|
| External Development Path | Path to the directory for external development areas. |
| Area Scrub Period | Period in days for cleaning the unused data in the file and module caches maintained by the data replication system for the development. |
| Data Replication Root Path | Path to the data replication root that holds the automatically-populated design data for the development. |
.