logo
search
Permission & Access Issues

How to Restrict Microsoft Project Web App Access to Stakeholders

Elise WilliamsElise Williams Oct 9, 2026 869 views

Question details

Administrators need to restrict access to sensitive projects in Microsoft Project Web App so that uninvolved users cannot open them, even in read-only mode.

How to Restrict Microsoft Project Web App Access to Specific Stakeholders
Product
Microsoft Project Web App (PWA)
Device & OS
not provided
Scenario
Protecting sensitive project data and timelines from non-stakeholders within an organization.
Observed behavior
Uninvolved users with broad organizational PWA access can currently view sensitive projects, requiring administrators to lock down permissions.
Before you start

Ensure you have Administrator privileges in Microsoft Project Web App (PWA) to modify security groups, categories, and project-level permissions.

Solution 1Recommended

Configure Security Groups and Categories in PWA

Adjust PWA security groups and project categories to ensure only assigned stakeholders have access to sensitive projects.

By default, PWA may grant broad read-only access to users across the organization. To secure a project, you must remove it from general access categories and assign it exclusively to a targeted security group.

1
Access PWA Settings

Log in to Project Web App as an administrator, click the gear icon in the top right corner, and select 'PWA Settings'.

2
Modify Project Categories

Under the Security section, click on 'Manage Categories'. Select the category that currently governs your sensitive projects to edit its visibility settings, ensuring broad read access is removed.

3
Assign Security Groups

Navigate back to 'Security' and select 'Manage Groups'. Choose or create the relevant stakeholder security group, and explicitly assign your sensitive project to this group only.

4
Verify Configuration

Test the new security configuration by logging in with a non-stakeholder account to verify they can no longer view or open the project, even in read-only mode.

Configure Security Groups and Categories in PWA
SharePoint Synchronization: If your PWA environment syncs permissions with a connected SharePoint site, updating these security groups will also restrict access to the project's document library and issues lists.
Free Microsoft Office alternative

Manage Project Documentation Securely with WPS Office

While Microsoft Project Web App requires complex permission management on the server side, you can securely handle all your project documentation, stakeholder reports, and planning spreadsheets for free using WPS Office. It provides a lightweight, highly compatible alternative for everyday document security.

  1. 1. Download WPS Office: Install WPS Office Free on your computer or mobile device.
  2. 2. Create Project Documents: Open WPS Spreadsheet or Writer to draft your project plans or stakeholder updates.
  3. 3. Encrypt for Stakeholders: Navigate to the 'Protect' or 'Security' tab and select 'Encrypt' to lock the file with a password before sharing it.
Highly compatible with Microsoft Word, Excel, and PowerPoint formats.Easily protect your project documents with built-in password encryption.Lightweight installation with an intuitive, familiar user interface.Free to use for creating and editing project plans and reports.
microsoft office alternative - wps office

Frequently Asked Questions

Why can non-stakeholders still see my project in PWA?

This typically happens because the project is associated with a broader PWA Security Category (like 'My Organization') that grants read-only access to all users. You must remove the project from general categories and assign it exclusively to a stakeholder-specific group.

Can I restrict read-only access for just one specific project?

Yes. You can create a unique security category for a single project and assign only the required users or groups to that category, ensuring no one else in the organization can view its details.

Will restricting PWA access affect assigned tasks?

If users are assigned to tasks within the project, they generally require at least 'Team Member' access to view and update their timesheets or task progress. Ensure that removing broad access does not accidentally revoke permissions for active assignees.