Would like to make different Contacts Public or Private. Many Projects have additional Owner and Engineer reps that need access to Project but whose information should not be accessible to all other Contacts of the Project.
Bobby Asbury
| Company | Leander Construction |
| Job Title / Role | Project Manager |
| I need it... | 1 month |
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.
© 2023 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.
Sam:
All I was thinking was to have a Private or Public check next to their Contact so, for example, a Subcontractor or Vendor could not easily contact the Owner (in most of our cases would be a City Entity) directly. I would think the "slimmer" approach making an individual that is marked "Private" not visible to a Collaborator or other lower tier security types. We also have some of our Staff that are indirectly associated with a Project but are not needed to be on a contact list but still need to access the Project.
We're looking into this as part of making roles more configurable and I've got a question for the group here. Is the driver for this request more like "I need absolute confidence no users will be able to see one another under any circumstances" or "I don't want it to be so easy for someone to export the whole project directory"? (or something else?)
I could see us approaching this in a couple of different ways:
A comprehensive approach ensuring for a certain role contacts are hidden from all places they could possibly be found, for example :
The Contacts tab
History/activity log
The workflow of submittals/RFIs/Issues
The Share menus in docs/drawings/photos
Item metadata (created by/modified by/etc fields)
A slimmer approach where we would hide the Contacts tab, but if that user was CC'd on an RFI with other contacts or went digging through the viewing history of a document they could see other contacts' name and org who had viewed the same item
Option 1 changes many areas of the product so I'm hoping there's a smaller-scale solution possible that still solves the core problem
Aaron
Yes, similar to other Private/Public items
Would a Private contact only be visible to specific users? Project Managers / Project Engineers / Project Editors?
I agree, we have contacts that we would like to view the page, but don't want subcontractors to have the ability to contact
Any review of this suggestion? Would be a very and seamingly simple way to add addition security for contacts while staying consistent to TEAM formats