Difference of Users vs Resources

E

Eric

I'm a bit confused about user and resources.
From what i know resources are people that are part of a project and users
are user for Project Web Access.

My question is what if i want to put a PWA user as a resource in a project?
I have this person who does not have a domain account (i cannot add him to
the resource pool by importing him from the active directory) so i just
created a user account(Project Server authentication) for him. How can i
allow project managers to include him in their project when his name does not
appear in the resource pool when they want to "add resources from Enterprise
Resources" in Project Proffesional.

ALso i cannot see users (that use Project Server Authentication) in the
Resource Center, i only see those who uses Windows Authentication to log in,
BTW i'm part of the administrators so i guess i'm supposed to see all
resources.
 
G

Gary L. Chefetz \(MVP\)

Eric:

All work resources entered into the Enterprise Resource pool get an account
in PWA and are therefore considered by the system to be "users." Please note
that if you define a resource as a machine, it still gets an account, even
though you're not obligated to count the machine among your licensed users.

A user is anyone with an account in Project Server. For instance, the built
in Administrator account is a PWA user, but doesn't appear in the resource
pool. You can't assign tasks to "Administrator." You may have people in your
company that want to be "users" in the system, such as Executives, who do
not wish to be included in the resource pool or available for work
assignments.

Anyone included in the Enterprise resource pool displays in the resource
center. Everyone with an account in the system do not necessarily appear
here, however they do appear under Admin > Manage Users and Groups > Users

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
 
E

Eric

Thank you very much.

Gary L. Chefetz (MVP) said:
Eric:

All work resources entered into the Enterprise Resource pool get an account
in PWA and are therefore considered by the system to be "users." Please note
that if you define a resource as a machine, it still gets an account, even
though you're not obligated to count the machine among your licensed users.

A user is anyone with an account in Project Server. For instance, the built
in Administrator account is a PWA user, but doesn't appear in the resource
pool. You can't assign tasks to "Administrator." You may have people in your
company that want to be "users" in the system, such as Executives, who do
not wish to be included in the resource pool or available for work
assignments.

Anyone included in the Enterprise resource pool displays in the resource
center. Everyone with an account in the system do not necessarily appear
here, however they do appear under Admin > Manage Users and Groups > Users

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Click to expand...
 
D

DimonD

Everyone with an account in the system do not necessarily appear
here, however they do appear under Admin > Manage Users and Groups > Users
Click to expand...

What means "do not necessarily appear"??? What is the filter? In which case
it will appear and in which not?

If I understood you correctly this means tha PWA users and Project Resource
are two different things/tables. But how do they differ?

If I create a Resource the PWA User is automatically created, right?
If I create a PWA User will the Resource be automatically created, or not
and why?
What is the link between this two (PWA Users and PWA Resources) entities?
 
G

Gary L. Chefetz [MVP]

DimonD:

When would you want someone to be a user but not a resource? For instance,
the president of your company may want to view the portfolio, but doesn't
want to be available for task work in the resource pool. Perhaps his admin
may need access to pull reports for the president, but he/she will never be
a resource for task work.

When you create a resource, a PWA user account is automatically created.
It's a safe assumption that a human resource will always be a PWA user. When
you create a PWA user through Manage users and groups, you create a user not
a resource.
 
D

DimonD

"Gary L. Chefetz [MVP]" пишет:
When you create a resource, a PWA user account is automatically created.
It's a safe assumption that a human resource will always be a PWA user. When
you create a PWA user through Manage users and groups, you create a user not
a resource.
Click to expand...

OK, I think that I understand you, but how can you comment this situation:
I have created several accounts for users using PWA Users and Groups. So
they are users but not resources now, right? I go to the PWA\Resources page
and see lots of resources but not this new users, right? BUT if I click on
the link View Resource Assignments (/Views/WebclientView.asp?_oid=-1) then I
see them in the list of availble resources!
Why???
 
G

Gary L. Chefetz [MVP]

DimonD:

The SharePoint list is not constrained to resources only. The system assumes
that all Windows account users can participate in the collaborative
features; again reflecting real-world scenarios. For instance, executives
may not have tasks in a project, however they may own issues and risks.
 
Top