This tab contains the following fields:
1. Enable Simple Upload - To enable simple upload on the project. You can overwrite this configuration at the project folder level. All new projects created after the Asite 20.0 Release will have simple upload enabled by default (can be edited later).
2. Enable Public Link - To enable public links on the project.
3. Mandatory Check Out Prompt - Have users see a checkout prompt while downloading files.
4. Mandatory Check Out Prompt (Restrict Download) - If a file is not checked out, restrict its download.
5. Publish Files as Private - To enable publishing of private files on the project.
6. Enable Object level visibility of private information - To define the visibility of any private files/forms at the object level (i.e. Distribution Group, Role, or Organization).
Enabling Object level visibility of private information is an optional feature.
This setting cannot be disabled later once it is enabled on a project (the related checkbox option would be disabled to deselect it later).
Suppose this setting is enabled on an existing project. In that case, any new users added to that specific object (i.e. Distribution Group/Role/Organization) and having access to the project will automatically get the visibility of private files/forms distributed to that object.
Click here to learn how to assign or remove visibility on files. Click here to learn about assigning or removing visibility on forms.
7. Enable Sharing XRefs to Project Teams - To share drawing files with external references on this project.
8. aMessages (File Comments) default - This setting will mark any new aMessage as private if the setting is marked as 'Private'. If set as 'Public', the user must manually mark an aMessage as private by selecting the option 'Mark as Private' while creating an aMessage if required. By default, it will be set as 'Public'.
If the 'Enable Comment Review' setting is enabled on the project, it will be replaced with 'File Reviews / Model Comments default'. It has two options: 'Private' and 'Public'. The default selected option while creating new projects is ‘Public’.
Select 'Private' to mark any new file reviews or model comments created on the project as private by default.
If 'Public' is selected, you can create new file reviews or model comments on the project as public by default. While creating a comment for review on a file or a comment on a model in such projects, you will have the option to mark the comment as private if required.
9. Enable Comment Review - Let your users review file comments based on the project's statuses that are enabled for review.
Enabling Comment Review is an optional feature.
This setting cannot be disabled later once it is enabled on a project (the related checkbox option would be disabled to deselect it later).
Comment review-enabled projects are not available to access from Classic View.
File aMessages will be called comments if comment review is enabled on the project. All comments created on files in a comment review-enabled project will be considered as part of a comment review process that can be managed separately.
Click here to understand how to create a comment review on a file.
If this setting is enabled on an existing project, any existing comment IDs will also change accordingly.
For example, if the existing comment ID on a file is COM001. Once 'Comment Review' is enabled on the project, it will show up as the review comment ID RC001.
10. Enable File Copy - Let users copy files on the project and place them in other project folders. Click here to learn how to copy files.
11. Include Watermarks on Print - When printing a file, include the purpose of issuing it and/or its status as a watermark.
12. Markup Options - Select the appropriate option for markups. If 'Save markup and open a discussion' is chosen, while saving any markup, a screen for creating aMessage appears. At the same time, your markup is getting saved and attached to the new aMessage under creation. If 'Save markup only' is selected, the markup created will be saved only. If 'Save markup and automatically send a discussion' is selected, created markup will be saved and a standard system aMessage will also be created automatically.
If the 'Enable Comment Review' setting is enabled on the project, the 'Markup Options' configuration option won't be available.
The project settings for new projects created after the Asite 19.7 release shall be set up with the default value of 'Save markup and automatically send a discussion' enabled.
13. Status Change notification - Select the appropriate option for the automatic creation of discussion upon the status change of files on this project. If 'Create Discussion Automatically' is selected, the checkbox option 'Create Discussion Automatically' that appears while changing the file status will show checked off by default. If not selected, the checkbox option 'Create Discussion Automatically' will appear and when changing the file status, it will show unchecked by default. Irrespective of whether selected or not, you can overwrite this configuration while changing the status of a file in that project.
All new projects created after the Asite 20.0 release will have the project setting 'Create Discussion Automatically' unchecked by default.
If the 'Enable Comment Review' setting is enabled on the project, the checkbox option 'Create Discussion Automatically' will be replaced with the checkbox option 'Create Review Automatically'. Select the appropriate option to automatically create a new review upon the status change of files on this project. If 'Create Review Automatically' is selected, the checkbox option 'Create Review Automatically' that appears while changing the file status will show checked by default. If not selected, the checkbox option 'Create Review Automatically' that appears while changing the file status will be unchecked by default. Irrespective of whether selected or not, you can overwrite this configuration while changing the status of a file in that project.
14. Enable Geotagging - To capture location-based geotagging information such as latitude, longitude, altitude, date, and time stamp for image files captured or uploaded using the Adoddle Field app. Capturing geo-tagging information for files is currently supported in the 'Files' and 'Quality' areas (not for files uploaded as attachments / secondary files). The captured file information includes latitude, longitude, altitude, date, and time stamp. If this setting is enabled, you'll need to give access to your mobile device location while uploading files from mobile apps (Adoddle Field or Asite Field).
To view geotag information available on existing form attachments and/or associations if any, click here.
15. Markup Privacy - This setting will allow users to define access to markups for other project users. If 'Public' is selected, all markups will be accessible to all project users. If 'Private' is selected, users can only view markups shared with them or accessible based on aMessage distributed to them. By default, this setting will be set as 'Public'. Click here for detailed help on viewing markups.
This setting won't be available if the 'Enable Comment Review' setting is enabled on the project.
16. Support QR Code - Enable or disable QR codes on files for the selected project. To learn how to configure the QR code for your project, click here.
Check: FAQs
Related Articles: Add a Project
Next Article: Add a Project - Configure QR Code