Search the Community
Showing results for tags 'request'.
Found 1 result
Hi All, I have a client currently who enjoy the concept of the Project Sharing features although wish for them to be used in a more global environment, unrestricted to a project file. They have quite detailed plans of their venues with specific things which should not be moved (diagonal bars, fixed height winch bars, fixed curtains, fixed orchestra pit deads, etc.). Commonly they will send these plans in the .vwx format to either external suppliers or prospective hirers who will send the plans back months later with their proposed changes. The problem is that often these external users will send back a plan with modification to the specific items above (moving grid pieces to locations which do not exist and/or places which have other obstructions, moving the pit to invalid stopping locations, etc). Often these changes go unnoticed until bump-in periods where conflict occurs as both parties believe they are in the right. The ideal would be the ability to password lock layers within the file. The ability to lock the 'Grid' layer for example and restricting the editing functionality, yet still allow class switching. Should the user need to move something in this layer they call in, receive the password and the file is logged with a change to that layer (possibly within the project sharing History). I'm aware we have referenced layers as an option although this has been tried and still required either a) releasing a second reference document or, b) the reference being broken and edited anyway. @JimWlet me know if I'm missing something here. Otherwise wishlist? Hope you're all well, J