Would be good to have a similar function to Aconex, InEight etc where we can assign permissions for users to send General Correspondence and RFI's, but keep the transmittal send permission separate. The transmittal function is a contractual submission and is usually managed by Document Controllers or individuals controlling the distribution of information between project participants, rather than an all user function.
|
Practical use of functionality?
Project teams use Deliverables Management to house all Transmittals, General Correspondence and RFI's in a single repository. Being able to assign separate Send permissions to users for only General Correspondence and RFI's enables communication to proceed within project teams, without the risk of individuals using the Transmittal function reserved for contractual submissions. |
|
|
What is the impact of not doing this?
Without the ability to turn on Send permissions specific to General Correspondence and RFI's, means that every user will only be presented with a "Send for Review" option. In this scenario, an individual with Send privileges will need to approve ALL general Correspondence sent on the project causing bottle necks which will have a time and cost impact to the project. However, we don't want to assign users the current overall send permission as this means the user can also send transmittals. This runs the risk of incorrect or duplicated information, which has not undergone quality checks, being shared as a contractual submission. This will make it impossible to control the information being shared. |
https://projectwise365.ideas.aha.io/ideas/PWDI-I-572 _ also raised here.
Thank you for your idea. We will consider this future enhancement into the overall picture of how role permissions are supported in Bentley Infrastructure Cloud when related to Correspondence and Communication functionality.