I was told, so maybe this has already changed, but why can't a collaborator have enough permissions to, start a new job or import from other places.
It would be nice if I could have my assistant do some of the menial tasks of adding pages, scaling, renaming, etc without taking up a "full" license.
Thanks for bringing up this important workflow question. You're highlighting what should be standard functionality for collaborators in modern takeoff software.
Collaborators should be able to perform these essential project management tasks:
The only restrictions should be on the core takeoff measurement tools:
Please have the Collaborator user Chat in from the zzTakeoff so we can work through this issue
Thanks for the input. We're planning to put out a patch later today or tomorrow to support these permissions in the Collaborator version.
We just deployed an update that will allow the permissions you requested. Now users with "Collaborator" license can help prep the project for takeoff.
This has been great, thanks for implementing it, BUT, when I presented this to my assistant, and changed her permission level from Takeoff to Collaborator, this is what made her head hurt.
The mass delete (being able to select more than one page at a time) is a huge deal for her. When she imports the plans, she needs to be able to delete all the other disciplines (MEP's for us) that we don't use and not being able too has her head spinning.
On a side note, I don't know if others feel this way, but to be honest, I get confused at where to post things like this, do I post in Q&A or Feature Requests. I feel like a lot of my questions, could turn into features, but where do I start, I'm not sure. Just my 2 cents.
Thanks for the feedback Perri. We'll get this fixed. This behavior was not intentional. Just some polishing we need to do on our permission system. We'll address it. Maybe we should merge Q & A with Feature requests. Not sure. As we get a lot more features in the software, I guess a lot more discussion may be about how to use formulas, templates, and assemblies, so that may separate the two in the long run.
Figured it wasn't intentional, just needed to be brought to your attention.
Thanks for all you guys do. Looking forward to growing with you guys.