Searching Capabilities on Project Sites

The project sites that are create by Project Server do not have a good searching capabilities compared to other SharePoint farms we have on our organization. On the admin side is there something that needs to be activated to allow for the searching capabilities
to filter through all the folders and documents?

Hi,
You can refer to this serie of 5 excellent blog posts about Project Server search capabilities written by a SharePoint MVP:
Part 1
Part 2
Part 3
Part 4
Part 5
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Similar Messages

Project Site custom list data reporting with Odata connection, BI reports in Project online 2013.

Hi,
Can we create an excel report with Odata feed connection which includes project site custom list data?
Example: My Project is "ProjectTest" and it has a project site in which i created a custom list "ProjectNotes" with some new columns. I want to include these columns in my report.
sandeep

Hello,
when using the SharePoint ODATA or REST APIs each list and site would have a different endpoint URL. Some example URLs are below:
REST API:
https://test.sharepoint.com/sites/pwa/Project01Test/_api/Web/Lists/getByTitle('ProjectNotes')/Items
https://test.sharepoint.com/sites/pwa/Project01Test/_api/Web/Lists/getByTitle('Risks')/Items
ODATA SVC:
https://test.sharepoint.com/sites/pwa/Project01Test/_vti_bin/listdata.svc/Issues
https://test.sharepoint.com/sites/pwa/Project01Test/_vti_bin/listdata.svc/ChangeRequests
The down site is that in Excel you cant dynamically update the connection URL so would have to add all of these in manually and create the data models - I guess this is ok if you don't have many projects and don't create many new projects. In code such as
JavaScript it is easy and you can build up the URL dynamically using variables like below:
projSiteUrl + "/_api/Web/Lists/getByTitle('ProjectNotes')/Items"
The options to explore to see if you have make this dynamic and get the data you want are:
Potentially look at the search API and use that in Excel:
http://sharepoint.stackexchange.com/questions/98159/retrieving-list-items-from-multiple-sites-via-odata-with-excel
http://social.technet.microsoft.com/Forums/windows/en-US/727c1893-6b42-478b-afca-b32fb259a53d/retrieve-custom-lists-from-all-projects-for-excel-reports-by-using-odata?forum=sharepointgeneral
Power Query:
http://blog.oraylis.de/2013/05/using-dynamic-parameter-values-in-power-query-queries/
JavaScript (put the data on a page), example:
http://gallery.technet.microsoft.com/scriptcenter/Server-Risks-and-Issues-on-65dcbe0e
Or bring the data down to a custom SQL database table and report of that data:
http://nearbaseline.com/blog/2014/04/project-site-custom-list-reporting-using-ssis-odata-connector/
Hope that helps
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server default groups when we create new project site

Hi,
When we create new project site in project server 2013 in site settings page some default groups are already present with some default permissions and some default members.
Interesting thing is that the members of these group are same when ever we create a new site.
Can you please help me understand, what these groups are, how they get created and how they are having some default members. Where are these members coming from.
Our project server is having project server permission mode.
Thanks,
Bhawna.

I briefly searched the MSTechNet but was not able to find a succinct article on this point for 2013, if someone has that, can they pls share. However, if you read most of the articles under this area,
you get the idea.
http://technet.microsoft.com/en-us/library/fp161361(v=office.15).aspx
From 2010 this applies and is still "similar"
http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
In 2013, for every Project Site (connected SharePoint site as it is now called in 2013), 2 Site specific SharePoint security groups are created: "SiteProjectName Project Managers (Project Web App Synchronized)"
& "SiteProjectName Team Members (Project Web App Synchronized)".
And Web Administrators (Project Web App Synchronized) is also created.
In addition, the default SharePoint groups for: Site Members, Site Owners, Site Visitors are present but remain empty.
Project Server controls the creation of these groups and the membership. The membership is a "formula" that goes something like this: If the user is the Project Owner then put them in the PM group.
If the user is a PWA Administrator, then put them in the Administrators group. If the user is a team member on the project, then put them in the Team Members group. There are other factors like RBS that are used in the formula.
Reading the descriptions of the groups reveals that for Project Managers =
Users who have Published this project or who have Save Project Permission in PWA.
For Team Members = Users who have assignments in this project in PWA.
I believe these are the old 2010 descriptions and actually Team Members = anyone who is part of the Build Team even if no assignments.
Further complicating matters is that if you are a site collection admin, you will see all the groups, for PWA and for all the project site (b/c you are actually seeing the site collection groups).
But only the ones mentioned above apply specifically to this project site.
Hope this sheds some light on the topic,
Thanks, Eric S. Pcubed

How to get the project name in a Reporting Services Report in a Project Site?

Hi,
I developed a report using Reporting Services where I need to choose a project to see the report. I want to include it in a Project Site template using a SSRS Web part. As the report will be in a project web site, I would like the report appears automatically
showing the project of the site without the need of choose of the project.
Can it be done without developing a complex code?
PS: Project Server 2013 and SQL Reporting Services 2012.
Thank you.
Best regards, Ricardo Segawa - Segawas Projetos / Microsoft Partner

Unfortunately there are a number of ways to navigate to a project site. (From Project Center is another) - Covering them all is not an option.
Like I said before there are two options, using a server-side web part - or using client-side code like the following: (just put this in a content editor on the page of your report and it will ensure there is a ProjUid on the query string)
<script
type="text/javascript">
//(c) 2014 James Boman - IPMO.
//License granted under creative commons CC BY-SA
//http://creativecommons.org/licenses/by-sa/3.0/au/
var PDP;
var web;
var ProjectUID;
var PWAURL;
ExecuteOrDelayUntilScriptLoaded(CheckProjectUid, "sp.js");
function CheckProjectUid() {
if (!urlHasProjectUid()) {
getAppWeb(function () {
getWebProperties(function () {
NavigateMe()
function urlHasProjectUid() {
strDest = document.URL
if (strDest.split('?').length
> 1) {
return (getQueryStringParameter('ProjUid')
!= null);
} else {
return
false;
function NavigateMe() {
var strDest = document.URL;
if (strDest.split('?').length
> 1) {
strDest += '&';
} else {
strDest += '?'
strDest += 'ProjUid=' + ProjectUID;
window.location = strDest;
function getAppWeb(functionToExecuteOnReady) {
var context = SP.ClientContext.get_current();
web = context.get_web();
context.load(web);
context.executeQueryAsync(functionToExecuteOnReady, onFailure);
function getWebProperties(functionToExecuteOnReady) {
webProperties = web.get_allProperties();
var context = SP.ClientContext.get_current();
context.load(webProperties);
context.executeQueryAsync(function () {
var allProperties = webProperties.get_fieldValues();
PWAURL = allProperties['PWAURL'];
ProjectUID = allProperties['MSPWAPROJUID'];
functionToExecuteOnReady();
, onFailure);
function onFailure(sender, args) {
alert('CSOM Error: ' + args.get_message());
function getQueryStringParameter(urlParameterKey) {
var params = document.URL.split('?')[1].split('&');
for (var
i = 0; i < params.length; i = i + 1) {
var singleParam = params[i].split('=');
if (singleParam[0] == urlParameterKey)
return decodeURIComponent(singleParam[1]);
</script>
James Boman - http://www.boman.biz Software Consultant for IPMO - http://www.ipmo.com.au

Manual creation of Project Site for a project is taking old project site template.

Dear All,
I have modified the project site and save it as a template to associate it with an EPT so that the modification will reflect in new project sites.
For existing projects, I am deleting the old project sites (after taking backup) and recreating so that new modifications will be there for existing projects and I am able to do so.
But, for 1 of the project, when I have deleted the project site and recreated, still it is taking the old template (i.e. new modifications has not been seen).
Kindly advice in some areas so that I can jump in and around and can find out a solution so that the project site will take modified project template.
Example to get the issue in an easy way:
ProjectA:
Project Site: http://epm/pwa/ProjectA
Issue List:
Column: Category [data type as Choice: Cat1, Cat2, Cat3]
Have saved 1 project site as a template and associated with an EPT with the following changes:
Column: Category [data type as Choice: Choice1, Choice2, Choice3]
Then, deleted the project site: http://epm/pwa/ProjectA and recreated.
So, it should take the modifications in the project site.
But, it is showing as Column: Category [data type as Choice: Cat1, Cat2, Cat3].
Regards,
Shravan

Dear Guillaume,
Thanks for your response.
Please seem my comments inline:
Which Project Server version do you use?
PS 2010
It is working well and as expected for all projects except for 1 specific project?
Yes. It is working well for other projects except 1 project.
Has this project something particular?
Nope. It is similar as other projects.
How do you proceed to create the new project site? Do you go to the site actions, then new site and pick up your new template?
First I have modified 1 of the project site and saved that site as a template.
Then, I have deleted the existing project site (from Project Sites under Operational Policies) and recreated so that project site will gets created from the new template. But, it's not happening.
Regards,
Shravan

On our project site, with Firefox 4 and 5, buttons don't take the keyboard focus if you mouse-click on them. Is this a problem of our site?

On a page like http://www.ori.uzh.ch/links.html, clicking a link opens a new tab, and after closing that tab, you can move to the next link with the tabulator key. On that site, it still works with Firefox 5. I also worked on our project site (password secured, sorry) with Firefox up to 3.6.18. But now, if I open a link with the mouse, close that tab again and press the tab key, the focus just goes to the first clickable button, as if I had not clicked any button previously. If I open a link by tab key and "enter", the keyboard focus is preserved on that button. But there are many many buttons on our pages, and they reload frequently.
BTW I adjusted the system preferences, so that the keyboard focus moves between all controls. (see http://www.tipstrs.com/tip/1505/Tab-key-to-select-form-elements-in-Firefox-on-the-Mac). But I don't think the problem is related to that.

I found out that our buttons are no links, but input tags, type="submit". I'll discuss the problem with our programmer.

Searching for a Project status = CLSD and open purchase orders?

Hi,
I am searching for a project status (Project Builder CJ20N) which allowed my to set a CLSD or a simillar status for settlement with open purchase orders.
This staus should allowed to process with open orders BUT not allowed to add new orders after setting this status.
Have somebody any idee? Or it is impossible?
Tahnk you in advanced for your Help.
Regards Baldy

Hi TV-kid,
while I was waiting for an answer I got to the same conclusion, so what you offers me is quite tempting actually.
I got a look to your website and it seems convincing. Still though, your case studies are in other business area, It's only a mater of good knowledge of File Maker.
I did download the test-drive last version of File Maker plus their samll Business Solution. I did read most of the documentation and the learning process would be too long to construct ourself a good crossed-data base.
I'd like to get in contact with you to look for a possible colaboration. to get private, I'd liketo do it through your contact link in your website .
To whom shall I write?
Thanks
Cheers
Cheers

Unable to Open Project Site Access Denied Issue Project 2013

This issue is happening to select projects and select project managers, they can view certain project sites but receive the error on other projects. After some extensive testing
it looks like if the PM is the owner of the project plan they are not getting added to any of the synced groups for the project site. I can change the project owner to any another PM and it processes correctly and adds them to the PM synced group on
the Project site. As soon as I make the original PM the Project plan owner again the previous PM gets removed from the PM synced group and added to the Team member synced group, the way its supposed to work. However the PM with the problem never
gets added to any group. I have to manually add them to the non-synced Owner group on the project site so they don't get removed from the synced PM group the next time the sync runs at midnight.
As I stated it is happening on select project plans and select PMs. I have tried replublishing the project plan via Project professional and the web and the results are the same.
If I create a new project plan and assign one of the PMs with the issue to the plan everything works correctly. We noticed the issue a few weeks ago; most of the plans with the issue are several months to a year old so they were working correctly until
recently. They had also made PM owner changes prior to the issue on most of those plans and everything worked correctly.
If anyone is experiencing this issue and has a fix please let me know. I am trying not to open an MS support ticket if possible.
Frank Miranda Florida Hospital MIS

I believe I've found the fix for this issue. After opening a ticket with MS support and not getting anywhere with this issue I decided to do an in-depth review of all the Project and SharePoint 2013 CU's starting with December 2013 to September 2014.
To my amazement buried inside the July 2014 CU was a hotfix for this issue described almost word for word. (I will list all the relevant KB's at the end) I contacted my support engineer inquiring about this hotfix and he stated it wasn't relevant because
the "Synchronize Project Web App permissions to Project Site" was not failing or even generating any warnings in our Prod or Test environments. I stated that is not always an indicator as ULS doesn't always catch all relevant errors.
I informed him that I also found a second hotfix pertaining to the same issue released August 2014, apparently the first hotfix in July didn't totally resolve the issue and a second hotfix was released. He was adamant that this would not resolve
our issue and he requested or production databases because he was unable to replicate the issue in his test environment. The reason, you may wonder, is because he was at a higher patch level that our farm.... Obviously! His farm had the most current
CU which included the hotfixes from July and August. Apparently he didn't see the flaw in his logic.
I decided to install the September CU on our test farm. Low and behold that fixed the problem, even though MS support stated the hotfix was not relevant to our issue. I learned a long time ago to take MS support comments as suggestions instead
of gospel truth, this isn't the first time they have confidently given me erroneous information.
We are currently doing further testing to verify that this CU didn't break something else. Unfortunately these rollups are not GA and Microsoft is very clear that you should only install them if the hotfixes pertain directly to your issue.
Finding the hotfixes was a chore as Microsoft loves to create multiple KB's for the same thing and then nest (bury) them so you have to dig through four or five KB's to find the relevant fix. I'll save you the trouble and list them below.
Watch the
September CU Webcast Brian Smith and team go into depth explaining why this issue has been happening and how they fixed it.
September 2014 CU http://support.microsoft.com/kb/2882990 (the one I installed)
August 2014 CU https://support.microsoft.com/kb/2989078
August Project site sync hotfix
https://support2.microsoft.com/kb/2883083
July 2014 CU http://support.microsoft.com/kb/2882990
July Project Site Sync hotfix http://support2.microsoft.com/kb/2882995
Microsoft Project Server Blog
http://blogs.technet.com/b/projectsupport/ (I find this to be more helpful than the TechNet site)
Frank Miranda Florida Hospital MIS

Unable to Open Project Site Access Denied Issue (Project Manager)

Hi
We got an issue that one project manager is having 12 projects, in that she can able to view 5 projects-- project sites but remaining 7 projects --- she is not able to open the project site (access denied) error is throwing when she try to open.
She is the project manager of the 12 projects and having project manager permissions on the project sites.
Please suggest any solution for this.
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

I believe I've found the fix for this issue. After opening a ticket with MS support and not getting anywhere with this issue I decided to do an in-depth review of all the Project and SharePoint 2013 CU's starting with December 2013 to September 2014.
To my amazement buried inside the July 2014 CU was a hotfix for this issue described almost word for word. (I will list all the relevant KB's at the end) I contacted my support engineer inquiring about this hotfix and he stated it wasn't relevant because
the "Synchronize Project Web App permissions to Project Site" was not failing or even generating any warnings in our Prod or Test environments. I stated that is not always an indicator as ULS doesn't always catch all relevant errors.
I informed him that I also found a second hotfix pertaining to the same issue released August 2014, apparently the first hotfix in July didn't totally resolve the issue and a second hotfix was released. He was adamant that this would not resolve
our issue and he requested or production databases because he was unable to replicate the issue in his test environment. The reason, you may wonder, is because he was at a higher patch level that our farm.... Obviously! His farm had the most current
CU which included the hotfixes from July and August. Apparently he didn't see the flaw in his logic.
I decided to install the September CU on our test farm. Low and behold that fixed the problem, even though MS support stated the hotfix was not relevant to our issue. I learned a long time ago to take MS support comments as suggestions instead
of gospel truth, this isn't the first time they have confidently given me erroneous information.
We are currently doing further testing to verify that this CU didn't break something else. Unfortunately these rollups are not GA and Microsoft is very clear that you should only install them if the hotfixes pertain directly to your issue.
Finding the hotfixes was a chore as Microsoft loves to create multiple KB's for the same thing and then nest (bury) them so you have to dig through four or five KB's to find the relevant fix. I'll save you the trouble and list them below.
Watch the
September CU Webcast Brian Smith and team go into depth explaining why this issue has been happening and how they fixed it.
September 2014 CU http://support.microsoft.com/kb/2882990 (the one I installed)
August 2014 CU https://support.microsoft.com/kb/2989078
August Project site sync hotfix
https://support2.microsoft.com/kb/2883083
July 2014 CU http://support.microsoft.com/kb/2882990
July Project Site Sync hotfix http://support2.microsoft.com/kb/2882995
Microsoft Project Server Blog
http://blogs.technet.com/b/projectsupport/ (I find this to be more helpful than the TechNet site)
Frank Miranda Florida Hospital MIS

Project Server 2010 Rename Project Site

I have a requirement, that is to change Projects' Names, it has to be done automatically (By code using PSI).
I used Project.QueueRenameProject and its working fine, however the associated project site/workspace is not renamed (updated).
I need suggestions about how can I rename the Project Site Programmatically (by code)?
I want the URL to use the new name.
I am thinking of two ideas, but I don't know the feasibility.
Idea 1, create a new site with the new name, copy the contents of the old site, and disassociate the old site, associate the new site, and delete the old one.
Idea 2, is to create a sharepoint/pwa event handler that triggers on Project Rename and execute what is mentioned in Idea 1.

Hi Mohammed,
What about using this method:
http://msdn.microsoft.com/en-us/library/gg178089(v=office.14).aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2010: PWA Removing Default Project Site Security Groups When Creating a New Project

I looked for this specific issue with Project Server 2010/PWA/SharePoint and could not find an exact answer... hopefully someone can help.
We are currently using Project Server 2010 and have a number of project site templates that are used dependent upon the enterprise project type selected. Each of these project site templates have unique permissions which should create the default security
groups on the project site upon publishing/syncing:
<Project Name> Members
<Project Name> Owners
<Project Name> Visitors
<Project Name> Project Managers (Project Web App Synchronized)
<Project Name> Team Members (Project Web App Synchronized)
Web Administrators (Project Web App Synchronized)
Whether a user creates a project through PWA or Project Pro 2010 and imports the project into PWA, we get a weird result in the Site Permissions of the newly created project site. PWA will remove all default security groups from the project site template
and add a whole list of users in the Site Permissions list without groups.
Once the project is published and the project site is created, we can then go back and add those default security groups back in the project Site Permissions and even add a couple of custom groups without them being removed on all subsequent project syncs
or publishing.
How do we get PWA to not overwrite the project site templates' security groups and place each user in the proper default security groups? At the same time, how is PWA adding a number of users into the Project Site Permissions?
Thanks in advance.

Paul,
Thanks for that information. Right now we are using the Test environment to turn the Auto-sync feature back on. I suspect that the reason this is happening is due to PWA groups/categories/security templates. There may be more than one PWA group that is "overwriting"
the default project site groups upon initial creation of the project. We will look further into the security settings to tighten up the policies.

Issue with Webparts while adding in Project Site

Hi
I am getting an error while adding web parts in project site page 2010. Below the steps
Open project site --> site actions --> edit page --> click on Add webpart --> ProjectWebApp --> Project fields --> Add
Please try and let me know is this possible or not
Regards
Santosh

Santosh,
The Project Fields webpart is ties to the PWA context, and cannot be added to Project Site.
There used to be a solution starter called Project Workspace Custom Fields webpart. You might want find and use that
An alternative is to develop your own SSRS report and display it in webpart..
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

How do I create a project site after I publish a project in Project Server 2013?

How do I create a project site after I publish a project from project pro 2013 in Project Server 2013? I'm trying to look for an option in the ribbon but haven't found any.
Thanks
James T.F

Hi James,
See in the article the procedure for site provisionning settings.
Note that the project site is created based on the template associated to the chosen project type (EPT) when the user first publishes his project. Be aware that if you allow the user to choose weither or not he'll create a sharepoint site when publishing
his project, he will be prompted in Project Pro with a dialog box giving the choice to create or not the site.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

How to Create a Custom Project Site Template Using Visual Studio

I know how to make changes and save a site as a template but I need to be able to create a new project site template during deployment to different environments. Trying to have this not be a manual process.

Hello,
This article might help:
http://blogs.msdn.com/b/sambetts/archive/2013/10/17/creating-a-clean-visual-studio-solution-from-a-sharepoint-2013-site-template.aspx
Start with a default Project Site (create a new site from the Project site template) and save out the WSP then import into VS.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2010 / Sharepoint 2010 Permissions not syncing to Project Site

Project Permissions not syncing to Project Site
Project Manager Group
New project is created and published project server sends permissions to Sharepoint which puts users into the following groups:
<dir><dir></dir></dir><dir><dir>
Web Administrator (Microsoft Project Server)
Project Managers (Microsoft Project Server)
Team members (Microsoft Project Server)
Readers (Microsoft Project Server)
At this time the creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager rights on the sharepoint site, and Admins will have Web Admin permissions.
Issue #1: Only the Web Admin permissions and creator/owner permissions are being added to the Sharepoint permission groups
Workaround #1: Going into the project site permissions and adding the
Project Managers (Microsoft Project Server) group manually and the sync will keep the permissions
Workaround #2: Going into the Server Settings, Manager Groups then removing or add all users to the No Permission Group, which forces an sync to all workspaces. Con: This workaround can only be down at night when users are not active since it will
block the queue for at least an hour.
Project Owner Transfer
Previously created project has owner change, once saved and published project server sends permissions to update user’s permission to
Project Managers (Microsoft Project Server) on Sharepoint project site.
Issue #2: When Project owner is changed and project is published the owner is not getting permissions to the Sharepoint project site. However, if owner is also added to the team using the Build Team Feature the sync will give the owner Project
Manager permissions on the Project Site.
Workaround #1: Going into Server Settings, Project Sites, select project and Synchronize. Once this is done, the owner will have Project Manager Permissions without being added to the team.
Users who have been added to this project in Project Server 2010, but not assigned to tasks. Users who have assignments in this project in Project Server 2010 and are contributors to the project workspace site,
meaning that they can create and edit documents, issues, and risks. Users who have published this project or who have
Save Project permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks. Users who have
Manage SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks.</dir></dir>

By default when you create project build team add users in the task and publish the project plan then All the User which are available in the project plan including Project owner will go to below mentioned group in project site:
1. creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager will get access to Project Managers (Microsoft Project Server)
2. User who are having team member access to PWA will get Team members (Microsoft Project Server) access if they are assigned to the project task.
3. User who are having team member access to PWA will get Readers (Microsoft Project Server) access if they are not assigned to the project task.
4. Only PWA Administrator will get the access to Web Administrator (Microsoft Project Server)
Sharepoint permission you have to use when you want to give permission manually to users on project site
In the Project Site provisioning setting under Server setting if you have Check to automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project
Server.
Then all the user get access as per describe above and if you will give access manually to any of the user either in project server group or in Sharepoint group once you will publish the project next time all the manually given permission will go away.
IF you want to give permission to user manually to sharepoint group or project server group then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions
change in Project Server.
You check PWA site setting --> Site permission then member of Sharepoint group user who will have access to sharepoint group in PWA site setting site permission will have access to all the project site sharepoint group as Project site inherit permission
from PWA root site.
Both the issue which you have described is behavior of project site.
For issue 2 when first time project owner create and publish the project and projectsite is getting created then porject owner name gets access in the porject manager (project server group) nect time if you will change the owner and publish the project
until he will not present in the project plan will not get the permission.
If you want to give sharepoint permission to users then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project Server and give
the permission manually.
Project site in 2010 has some issue and not full filling customer need some time ,Ms has came up with 2013 which is having tight integration with project sites .
Project workspace security groups are equal to the SharePoint Server 2010 security groups.
Web Administrator equals Full Control
Project Managers equals Design
Team members equals Contribute
Readers equals Read
Users who have Manage
SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can
create and edit documents, issues, and risks will get access to Web Administrator (Microsoft Project Server)
http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
kirtesh

Searching Capabilities on Project Sites

Similar Messages

Maybe you are looking for