Overview
Confidential Projects are designed with enhanced security measures to protect sensitive information. These security requirements result in specific limitations and functionality changes that differ from standard projects. This guide explains these modifications and helps you understand how to work effectively within a confidential project environment.
Getting Started: If you're new to confidential projects, please first review our Creating Confidential Projects Guide to learn how to set up your first confidential project.
Why These Limitations Exist
Confidential Projects operate on a zero-trust security model, meaning:
No automatic sharing or exposure of information
Explicit permission required for all access
Complete isolation from organization-wide analytics and reporting
Administrator oversight for all access control changes
These measures ensure that sensitive information remains protected and accessible only to those with explicit authorization.
Access Control Limitations
1. Project Creation - Administrators Only
Limitation: Only administrators can create confidential projects.
Why This Matters: Creating a confidential project requires understanding of security implications and proper access control management. Administrator-only creation ensures:
Proper evaluation of whether confidentiality is necessary
Consistent application of security standards
Centralized oversight of sensitive projects
2. Collaborator Management - Administrator Restricted
Limitation: Only administrators can add collaborators to confidential projects.
Critical Impact: When non-administrator users attempt to collaborate, the following restrictions apply:
@Mentions: If a user mentions someone not already in the project, that person will not receive notifications or gain access
Assignments: Assigning tasks to users outside the project will not grant them access
Comments: Referenced users in comments cannot see the content unless previously added
Important: If collaboration is blocked, non-admin users must request an administrator to explicitly add the required collaborators through the Edit Project page.
Workflow Recommendation:
Plan your team composition before starting work
Have an administrator add all necessary collaborators upfront
Maintain a list of pending access requests for administrator review
Communicate access needs through secure channels outside the project
3. Project Ownership Updates
Limitation: Only administrators can update project owners.
4. Customer Ownership Management
Limitation: Only administrators can update customer owners.
Content and Data Restrictions
5. Response Library Automation Disabled
Limitation: Responses are never automatically added to the library for confidential projects.
What This Means:
The "Save Responses to be used in future projects" setting is permanently disabled
Approved responses won't appear in organization-wide libraries
Knowledge sharing happens only through manual, intentional actions
6. Analytics and Insights Exclusion
Limitation: Confidential projects and their data are completely excluded from organizational insights and reports.
Affected Features:
Automation Reports - No data from confidential projects appears
Gap Analysis - Confidential project information is not included