PWA access vs. Projects access

[Dimondwoof]

Okay, this product confuses the hell out of me. You can setup users to
access the Project Server Web Access, but they are not the same as people who
can access the projects via the Project client. And you can setup "sites"
and "workspaces" but you can't specify where projects are saved so everyone
who can access the server via the client has access to all projects. It
looks to me like there are 2 completely products mashed together here.

Am I missing something? Is there really no way to separate out who gets to
see what projects?

I have to say, this product has the WORST management interface that I have
ever seen on a server product! What a piece of garbage!

 

[Ben Howard]

Yes, you are missing something...

The 1st rule of project server is learn and understand the security (groups,
categories, permissions etc), and that each user's access depends on the
different permissions they accumulate through the groups that they belong to.
Once this is understood, then it becomes apparent that each user is set up
once only, and some users might only access the server in the DB via PWA, and
some might use both PWA and Project - depends on their group membership.
Also, users (by default) get the rights to see only the projects they have an
interest in, not all projects on the server. So, if I'm just a team member,
I only get to see the projects that I have been assigned to.

Everything is stored in a DB, safe, secure, and not open to everyone!

 

[Dimondwoof]

Thanks for the info Ben.

Although, apparently I'm still missing something, because you mention that
users are only setup once. But I had to set up 2 different users if I wanted
access through both PWA and Project. If I only have to setup a user once,
why don't the users I setup via Project show up in PWA and vise versa? And I
setup a user in PWA who could access that but not through Project until I set
him up through that interface as well. Also, users that I setup through
Project can't access PWA until I set them up separately in there. So it sure
doesn't look like you only set a user up once.

 

[Ben Howard]

Simply put, you didn't do it right, and I'm not going to guess what went
wrong. Users can be set up in PWA, in the resource centre. Resources can be
set up here too, and optionally, in Project Pro too; you have the choice as
to the best way for you. You do not need to set them up twice - no way.

 

[Dimondwoof]

Yep, I'm must have messed it up somehow. Like I said, the management part of
this software is complete crap. Oh well, I guess I'll keep slogging through
the useless "documentation" until I can find anything that tells me something
useful.

Thanks

 

[James Fraser]

Yep, I'm must have messed it up somehow.

From the problem you've run into, I'll make a few guesses:

1) You're using Project Server 2003.
2) When adding a user to the Enterprise Resource pool, you didn't
specify their "Windows User Account" (You need to add that column to
the view.)

In Project Server, a resource (i.e. a person who can be assigned to
projects and tasks) is not necessarily the same as a user ( a person
who can log in to the server and use server features.) Most acccounts/
resources/users will be both, but there are some cases that will only
be one or the other. Some examples of when one is just one or the
other: An executive (CEO, for example) who can not be assigned to
tasks, but needs access to reports will not be a resource, but will be
a user. This person should not be set up in the resource pool, but
only through PWA. A generic resource ("Database Admin Level II") can
not enter time, but can be assigned to tasks, so should be entered
into the Enterprise Resource Pool, but not as a user.

When you add a user to the ERP and specify their Windows User Account
field, then they are created as a both a resource and a user.

If my guess is wrong and you are using 2007, then pay attention to the
check box for "User can be assigned to tasks."


Hope this helps...
James Fraser