Using deliverables/dependencies issue

[Eric_H]

Ok, after taking a GREAT CLASS with some of the folks that frequent this
forum I am trying to set up my security correctly (wis I had that class
earlier!), per a customer requirement, I need to have several organizations
that maintain schedules, each has read permissions for all schedules in the
server and using RBS I have assigned each team member to their organizations
so I can allow write access to only files in their perspective organization.
HOWEVER, the need to use dependencies that were created in schedules out
side their organization. Manage dependencies on deliverables does not show
any schedules that the planner does not have read/write access to...
obviously I could make all schedules read/write to all planners, but that
defeats my customer rules, I need to make all schedules readable, and some
schedules read/write but yet still allow deliverables to be available
enterprise wide... What am I missing??? any advice?

 

[Dale Howard [MVP]]

Eric_H --

I suspect that the GREAT CLASS you took was one of our company's open
enrollment classes. If so, thanks for the kind compliment.

Regarding your security requirements, you are not missing anything. Your
customer's requirements are in conflict with one another. The customer
cannot have it both ways. If the customer wishes to use the Deliverable
Dependency functionality, the customer's PMs will need to have Read/Write
access to all projects in the system.

So, it's time to go back to the customer, tell the customer that their
requirements are in conflict, and tell them they cannot have it both ways.
Let the customer decide which is more important: having Read-Only access to
projects not in your part of the organization, or having Read/Write access
to use the Deliverable Dependency functionality. The customer has to make a
decision which is more important to the organization. Hope this helps.

 

[Eric_H]

Yes Dale the class was with your company, and IT WAS GREAT I cannot recommend
your folks enough (real client, not an actor and not paid for my plug) (call
MS Project Experts.)... so back to the issue... Is there any work around for
this? What if I simply cannot change the rules? It doesnt make much sense
that you need to have write access to utilize a deliverable for a dependency.
All really should need is to see the deliverable, not edit it...

 

[Dale Howard [MVP]]

Eric --

I am not aware of any workaround to this issue. If the system requires
Read/Write access to creat the Deliverable dependency, then so be it.
That's why I said you should inform your customer about this, tell them that
this is how the system works and that it cannot be changed, and then let the
customer decide which of their two requirements are the most important.
Hope this helps.