Skip to Main Content
Coming Soon: On April 2nd, all Suggestion Boxes will be migrating to The Network, Trimble's online user community. Your posts, votes, comments, and user accounts will transfer. This site will become read-only after the migration, and this banner will have a link to the new location for ProjectSight suggestions.
Categories File Library
Created by Brendan Radich
Created on Jul 25, 2023

Permissions for Linked Files from Other Record Types

When we create PCOs, we upload change order backup from our subcontractors to the PCO line items or PCO directly. Then, when we turn that PCO into a COR, we link that same backup from the File Library to the COR, so that it is easy to print a complete package (since ProjectSight does not support printing linked records & backup).

The problem we encounter with this is that we don't give owners & architects access to all CORs and we don't usually want them to have access to PCOs---we have those record types to only grant access to participating companies. With this workflow, anyone outside our company that has been added to the COR will not see the files we've linked from the File Library (File Library > PCO > PCO Item > File).

There are two workarounds to this currently, neither of which are ideal:

  1. We can download a copy of the file from the PCO or File Library, and upload a separate copy directly to the COR.

  2. We can invite individuals from outside our company to the PCO, which might give them data we don't want them to see.

My Proposed Solution:

Have either a Portfolio/Project-level Setting or ad-hoc option to control a new feature where, when linking from the File Library, PS will make a new copy of the file to the new record's folder within the File Library, thus inheriting the new records permissions.

  • Attach files