Advisability of removing default groups and rolling my own

[wbbusby]

I admin what I'm learning is a small to mid-size environment (approx 450
resources and averaging 500 - 600 new projects annually). With a couple dozen
project managers. Our people fall into groups such as
- Executives
- Managers
- Project Managers
- Staff
Most of the above map pretty well with existing default groups. I tend
towards wanting Project Server to bend to our nomenclature and either
customize (including renaming) the default groups to mine and remove any
extraneous ones. Of course, we've had tools that make that decision painful
when upgrades are applied or the tool tries to apply some default behavior.
Would there be any potential issues with default behavior if I removed the
following groups
- Portfolio Manager
- Team Lead
and renamed the others to more closely represent our names for the groups?

 

[Dale Howard [MVP]]

wbbusby --

For the sake of simplicity, I would not recommend renaming any of the
default Groups, nor would I recommend removing any of these default Groups.
I would recommend that you use the default Groups and set permissions as you
need to do in your own environment. Just an opinion, however. Perhaps the
others have some ideas for you as well. Hope this helps.

 

[mark.everett]

Wbbusby:

First of all, I don't think you can remove the default groups. Just
confirmed that. It gives you message asking if you are sure you want
to delete the group, then gives you a message saying you can't delete a
predefined group.

Regardless, I like to leave the default groups as, well, default. They
are always there to fall back on in case something gets messed up (not
that I would have any personal knowledge of that) .

I like to create new groups, specific to the client requirements. So
Team Member might become Staff - Client Name. I do that with Groups,
Categories and Views. It might make the lists a little busy, but at
least you are sure that you are working on the correct data when doing
configuration. This is especially important when testing a change.

I think Dale's advice is valid too - but prefer to work the way I do,
as long as the client agrees. Your mileage may vary.

Hope this helps,
Mark S. Everett | PMP
www.quantumpm.com

 

[John]

I tend to agree with Mark's approach. I use the default groups as templates
and copy their permissions to new groups that I've created to model our
organization. I may have several groups that have the identical permissions
sets, but it is invaluable (administratively) to place a new sysadmin in the
sysadmin group and category.