This idea has been merged into another idea. To comment or vote on this idea, please visit MVPM-I-304 Need Customizable Security Groups or Add More.
The new markup of documents is great, but only to Project Editors which is limited to only 1 or 2 people on the project. Since a Collaborator's permissions allow them to upload and replace a document, they should then be allowed to markup a document. They are shown all the markup options so it appears to them that they can markup, but then get a permission error.
If they cannot markup, the markup options should be hidden from those users so they are aware they can't save their changes.
Mercedes Green
| Company | Skygrid |
| 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.
This is a must. Surprisingly, we were sold that this functionality was available. Even our trainers did not explain this wasn't possible. For our users in the field, they need to be able to mark up document such as PO Receivers and Drawings to state they have received something or an area has been completed. It defeats the purpose of having this out in the field if they cannot use it.
Makes sense, we're fixing one scenario where users see the markup tools even though they don't have access in the next release.
We have more elaborate folder security options planned for the near term, so this will give us much better control over who can do what. So essentially if you're an 'Editor' on a folder, you'll be able to markup documents within there. Today we're a bit limited on this by our folder roles inheriting from your project role and erred on the side of least access in the first release.
Only public markups would affect versioning, private would only be seen by the user who created them until they became public and were added to a new version.
If we can supply security to a folder and have that security determine not only who can see but who can also upload and markup, that is what we would need. Our Project Editors are not the creator of these drawings (we are only project managers of the project) so our Project Editors aren't the ones making the majority of the markups. Our consultants should be able to mark them up for all to see. If a collaborator can download, markup then re-upload, it's the same as allowing them to markup "live."
As well, it would be helpful to remove the markup tools on the pdf if the user does not have access to markup. It gives them a false sense that they can markup so if they spend a lot of time making markups then get a permission error, it may cause some grievance.
If there are both private and public markups, how would that affect the versioning? We don't require hiding markups from users. If you can access the file, you can see all the markups. If a person has to now be responsible for maintaining all of the public or private markups and allow, disallow etc, that's a lot of work.
This is definitely something we intend to do in the future. We're just keeping it tight in the first iterations as we've heard from many users that they want to be super tight on who's allowed to change information on a drawing that the whole team can see.
Our current thought is that these are 'public markups' and we'll add 'private markups' that anyone can add to a document. Then there will be some path for a user to request that a private markup be promoted to a 'public' markup and approved by the proper user on a project before being made public.
Does that fit with your need? If not, interested in the flow you see for collaborators adding markups.