PWA Access and Proposals

[KeithR]

We frequently allow access to project workspaces for consultants,
contractors, etc. that are not part of the enterprise resource pool. For our
needs, that works fine as long as the workspace belongs to a *project*.

However, this is one thing that doesn't appear to work the same if the
workspace belong to a *proposal* (there are others - and finding
information/documentation is not easy).

Does anyone have hints/tips/recommendations for understanding and addressing
this type of difference between *proposal* and *project* workspaces?

Thanks in advance - I get a lot of useful information from this forum!

 

[Ben Howard [MVP]]

Hi Keith, the difference between proposals and projects is purely in their
client, ie a browser and MSProject. WSS sites are created, and the
permissions synchronised in exactly the same way. Do you add resources to
your Projects which are not added to your proposals? (I know you said that
these consultants are not part of the ERP, but I just want to make sure...)

 

[Gary L. Chefetz]

The problem is that he's using resource plans and making no assignments.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

 

[KeithR]

That is correct - as long as it is a proposal, we leaveit as a resource plan.
Once we promote to a project, we upgrade to a full project plan with task
assignments.

So - is your 'best practice' recommendation to include tasks and assignments
at the proposal stage? If so, that should address this problem?

 

[Gary L. Chefetz]

Keith:

You could add a task called "View Project Workspace," assign resources to
it, publish and it solves your problem. Whether or not this is a "best
practice" or not, I can't say, but it is a good workaround.

 

[KeithR]

Thanks, Gary. I will adopt that method - appreciate your help.