Submit Your Suggestions for Viewpoint Team

Is this on the product backlog yet? It's crazy that this was even implemented in the first place.

This is essential for using VP Team. This is causing MAJOR bottlenecks when trying to set up new jobs!

Project editors and PCs need the ability to set up people as the project managers. Please revert back

PCs are responsible for setting up all projects. We need to be able to set up project managers in the system. Please change back so that PCs have this function.

This is the most inconvenient feature when setting up a project, and silly might I add. It's the PC's responsibility so it makes no sense why this function was taken away from that role. Not only does it slow down the process, but it could also delay it depending on who in your company does have this responsibility. It needs to return to role of the PC immediately if not sooner.

PCs are responsible for setting up all projects. We need to be able to set up project managers in the system. Please change back so that PCs have this function.

Project editors should definitely be able to make someone a project manager on any job. As I, a project editor / coordinator, am the one setting up projects and adding contacts to the job, I should have the access to make someone a project manager. It is very inefficient for me to go to the enterprise admin and have them change someone's collaboration type to project manager.

Project editors need the ability to set up people as the project managers. It is not an efficient way for me as the project editor having to email the Enterprise admin to change someone's collaboration type to project manager each time I set up a project.

Project Managers here do not set up the jobs, Project Coordinators do. Please change this back so PCs can do this function again.

Project Editors and or Project admins need to be able to set up people as project managers. it is just silly for the enterprise admins to be the only ones. That is just crazy!

Can we please get this fixed. There are only two of us that add projects to Team. When we do, we add our Project Coordinators as Project Editors and they setup the projects and add all contacts. Once this happens, they can no longer add Project Managers to the project.

Just for reference since this change occured around Sept, IT has been asked 32 seperate times to add Project Editors as Project Managers in Team as of Dec 30th.

The whole issue around this is that our Project Assistants setup the projects in Team and it adds them as a Project Editor. Once this happens, they can no longer add Project Managers to the project. If they changed it so that the person setting up the project was a Project Manager by default, then it would fix the issue. If the person wasn't supposed to be a Project Manager on the project, they could then demote themselves. Or, you could just make it so Project Editors can assign other people the role of Project Manager, just not themselves.

We are having the same issue. In our company our office administrators are responsible for creating projects. If they set themselves as Project Editors, they are no longer able to add Project Managers. We do not want all of our company or all of our administrative staff to have Admin User level access to this software, that is a security issue no matter what company you work for. We have to have a way for the people setting up projects (i.e. Project Editors) to add Project Managers. We now have to submit individual tickets to our IT for them to add users for every project we create. We create about 25-50 projects a month. Not being able to add contacts for the people setting up the projects to finish job set up is completely halting out company right now. We are unable to use this software effectively because we literally don't have permission to use it!!!!! This HAS to be fixed immediately!

Only 3 people in our company have Admin permissions in Team in order to reduce the possibility of major errors. The people that setup new projects don’t have Admin Access and therefore aren’t able to add Project Managers to new projects. They are also not able to add themselves as a Project Manager and must request from IT every time a new project is created (we create many projects a week). This is causing a serious halt/bottle neck to our company, since only IT has the ability to add a project manager to new projects.

We are unable to actually use VP Team given this change and need it revered ASAP!

Thanks for raising this everyone - it was an internal oversight that Project Communications aren't allowed to invite users to the Project Manager role. We will get this corrected.

EXACTLY! we have 26 offices and only our IT Dept has Enter Admin rights. We do not have the time to add people to projects because they can't now. Not a smart move. Maybe add another security level for project permissions, but we cannot have them with ENTER ADMIN access. They will screw something else up and start changing things they should NOT have access to.