PWA Update Menu

[PatK]

If anyone can figure this out, I will be eternally in your debt!

On our PWA interface, we have the typical "Update" menu, with the following
three items listed on it as menu options:
- View task changes submitted by resources
- Set rules for automatically accepting changes
- View history of past task changes

A few weeks ago, we could see, just fine, bullets 1 and 3. Now, for
whatever reason (and we don't know if the admin tweeked something he did not
knowabout), but we now only see the second bullet. Thus, our PMs cannot
update their MS Project files with updated status information.

The above items were cut right out of the Server Configuration, Menus
screen, so the items are configured to be visible, but yet, we cannot see two
very important items. HELP!!

Pat

 

[PatK]

One more thing, and I do not know if this helps:
- I get an error: The Active Directory group partially failed to
synchronize with the Enterprise Resource Pool on 11/8/2005 at 8:51 AM.

In otherwords, it does not seem to be able to sync a validate global group
(domain\groupname). Wondering if a service is missing.

Also, as the ADMIN, I "can" see the Update menu just as I want, but the
ADMIN is the only user that can...the rest see only the single rule:
- Set rules for automatically accepting changes

Don't know if that helps at all.

 

[PatK]

Figured it out, and it was as I suspected. An admin had given our Project
Managers not only a PM permission, but also one we call Team Member (far more
restrictive). It appears that MSPS gives you the LEAST capable permissions
in ambigous configurations. Anyway, removed the lesser level of permissions
from the impacted users, and everything appears to be working again!

Am posting this only for someone else that may do something similar...

 

[Reid McTaggart]

Your Team Members group must have some permissions set to Deny. This is a
bad practice, because all additions to the resource pool are automatically
set up as Team Members. Having to remove someone from this default group is
an extra administrative step that will undoubtedly cause trouble again.

Deny should be used very sparingly, and only when the person doing the
setting understands completely and precisely what he is doing.

 

[PatK]

You are correct...we had two groups, Team Members and Project Managers. One
was set to Deny (team members) and one to allow (Project Managers). I think
the admin person inadvertantly changed us, because only two of the PMs were
affected, while the rest had no issue at all. Once he removed us from the
Team Members group, all was well (and I may not be using correct terminology
there...but you sound like you know what up.). Thanks for response!!

Pat