Confidential Projects and Permissions
Locking down a project workspace after Control Center creates it.
This is a manual admin task with a real exposure risk. Control Center creates every project workspace with default sharing. For a confidential project, that means people who shouldn't see it can — until you fix it. Act on the alert promptly.
You'll receive: "Confidential project - please lock down permissions — "
Step 1 — Open the workspace
Click the Project Link in the alert email.
Step 2 — Open sharing
Click the down arrow next to the Share button (top right of the dashboard), then select Share workspace.
A pop-up opens showing everyone currently shared to the workspace.
Step 3 — Remove who shouldn't be there
Click Manage access, hover to the end of a user's row, and click the X that appears.
You will need to remove the Power User group. Remove any other users who shouldn't have access.
Step 4 — Add who should be there
In Add people by name/email, add the correct people. Typically:
- Project Leader
- Sponsoring GM
- Project team members mapped for that submission
If you're unsure who belongs, check with the Sponsoring GM before adding anyone back.
Step 5 — Set the permission level
Set each user to Editor - can share before adding them.
Step 6 — Record the action
Open the Project Intake Sheet, find the project row, and tick Access Restricted.
Access Restricted is highlighted yellow for confidential projects so it stands out, and turns grey once ticked. Yellow means the job isn't done.
Confirming it worked
The Project Leader receives: "All set — (Confidential)"
Related articles
- Intake Automations and Approval Routing
- The Project Intake Sheet