Activating Permission Group

R

Ruth Halbach

Hello, I just migrated 2003 data to Project Server 2007. I created new
permission groups and new categories. However, when I assign the permission
groups to resources, they do not inherit the permission or categories defined
by the group. I must be missing something, but I've searched & researched
and come up empty. Does anyone have any suggestions on what I might be
missing?
 
J

Jonathan Sofer

What is it exactly that isn't working with your permissions? Have you
verified that the new groups are attached to the the new categories with the
appropriate category permissions enabled?

Have you also verified that your resources have the "Resource can logon to
Project Server" checkbox enabled on their resource accounts in PWA?

Jonathan
 
J

James Fraser

Hello, I just migrated 2003 data to Project Server 2007. I created new
permission groups and new categories. However, when I assign the permission
groups to resources, they do not inherit the permission or categories defined
by the group. I must be missing something, but I've searched & researched
and come up empty. Does anyone have any suggestions on what I might be
missing?
Click to expand...

Ruth,

I haven't run into or heard of anything like this. You've probably
already double checked, but it may be worth looking again: are the
categories and groups set up correctly? Are you using the new groups
you created and not the ones that were migrated?

What particular permission are you using to test with? Maybe something
about that feature is different in 2007 than what you expect?


James Fraser
 
J

James Fraser

Thanks for the responses. Let me better explain what the issue is.

Setup: I created new categories and permissions groups. The definition for
the group contains the new categories. eg: Tool Administrator group has all
permissions flagged as 'Allow' and all categories chosen. The additional
permissions associated with each category have also been marked 'Allow' for
each option.

Action: I assign myself to the Tool Administrator group. I open the client
and create a new project. I then attempt to save the project and see an
error messages stating that I do not have sufficient permission to add a
project to the server. All PWA permissions are enabled.
Click to expand...

Have you verified that one of the categories on which you have "Save
Project to Project Server" permission is set to include "All current
and future projects in Project Server database" in the "Projects"
section? As a default, the My Organization category is set this way.
But if you created all new categories, you will need to set one up
manually.


James Fraser
 
R

Ruth Halbach

Yes James. In fact, every category has every setting checked for this
permission group. I went into Manage Categories and made sure that each one
was set to include "All current and future projects in Project Server
database" in the "Projects" section. I removed all of the checked
permissions below that so I wasn't excluding anything in case that was the
problem. I again tried to create a new project and again received the error
that I did not have sufficient permissions.

Thanks again for your assistance, Ruth
 
C

Clara

I have the same issue, Ruth. I used the security templates labeled
ProjectServer2007, set my permissions and saved. I then used the default
categories and applied the templates. Then I made sure the various groups
were in the categories, and users were in the correct groups. All PWA
permissions are granted as well. So, a Team Member in the ProjectServer2007
Team Member group should have the My Tasks category, which, uses the Team
Member security template. Definitely I have allowed the ability to log on,
for instance. But the users are unable to log on until I open the user in
Manager Users and apply the darned templates. No inheritance appears to be
happening. Did you ever get an answer for this?
 
R

Ruth Halbach

Clara, I started over. I deleted everything I had created, copied the
security templates to my own version and modified them. Copied the
categories to my own version and modified them. Copied the groups to my own
version and modified them using modified template. Then I assigned only one
group to a user. Doing it in this order seemed to do the trick.

Ruth
 
Top