Article Summary
Confidential projects operate with enhanced security measures that result in specific limitations and functionality changes. These modifications ensure sensitive information remains protected and accessible only to explicitly authorized users. Understanding these restrictions helps you work effectively within confidential environments while maintaining security standards.
Estimated Time
3-5 minutes
Prerequisites
Familiarity with standard AutoRFP project workflows
Understanding of your organization's confidential project policies
Access to a confidential project
🔒 Why These Limitations Exist
Confidential projects operate on a zero-trust security model that prioritizes data protection through:
No automatic sharing - Information is never exposed without explicit permission
Explicit authorization required - All access must be deliberately granted by administrators
Complete isolation - Confidential data is excluded from organization-wide analytics and reporting
Centralized oversight - Administrator control ensures consistent security standards
These measures guarantee that sensitive information remains protected and accessible only to those with proper authorization.
💡 New to confidential projects? Please first review our Creating Confidential Projects Guide to learn how to set up your first confidential project.
Access Control Limitations
Limitation 1: Project Creation (Administrator-Only Access)
What's Restricted: Only administrators can create confidential projects.
Why This Matters: Creating confidential projects requires understanding security implications and proper access control management. Administrator-only creation ensures:
Proper evaluation of whether confidentiality is necessary
Consistent application of security standards across all sensitive projects
Centralized oversight of confidential workspaces
Limitation 2: Collaborator Management (Administrator-Restricted)
What's Restricted: Only administrators can add collaborators to confidential projects.
Critical Impact: When non-administrator users attempt to collaborate, the following restrictions apply:
@Mentions - Mentioned users who aren't already in the project won't receive notifications or gain access
Assignments - Assigning tasks to users outside the project won't grant them access
Comments - Users referenced in comments cannot see the content unless previously added by an administrator
‼️ Important: If you need to collaborate with someone not yet added to the project, you must request an administrator to explicitly add them through the Edit Project page.
Workflow Recommendation:
Plan your complete team composition before starting work.
Have an administrator add all necessary collaborators upfront during project creation.
Maintain a list of pending access requests for administrator review.
Communicate access needs through secure channels outside the project environment.
Limitation 3: Project Ownership Updates
What's Restricted: Only administrators can update project owners.
Why This Matters: Project ownership changes in confidential environments require administrator oversight to ensure proper authorization and accountability.
Limitation 4: Customer Ownership Management
What's Restricted: Only administrators can update customer owners.
Why This Matters: Customer ownership assignments affect access to sensitive client information and require centralized control.
Content and Data Restrictions
Limitation 5: Response Library Automation Disabled
What's Restricted: 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 during confidential project creation
Approved responses won't automatically appear in organization-wide libraries
Knowledge sharing happens only through manual, intentional actions
How to Work With This: You can still manually add appropriate responses to libraries when the content is no longer confidential or has been cleared for broader use.
Limitation 6: Analytics and Insights Exclusion
What's Restricted: Confidential projects and their data are completely excluded from organizational insights and reports.
Affected Features:
Automation Reports - No data from confidential projects appears in automation metrics
Gap Analysis - Confidential project information is not included in content gap assessments
Organization-wide dashboards - Confidential project activity is isolated from general reporting
Why This Matters: This isolation prevents inadvertent disclosure of sensitive information through aggregated reporting and ensures confidential data remains completely separate from standard organizational analytics.
💡 Tips & Best Practices
Plan ahead - Identify all required collaborators before project creation to avoid access delays
Document access requests - Keep a running list of who needs access and why for administrator review
Communicate proactively - Let team members know when they'll be working on confidential projects so they understand access restrictions
✋🏼 Common Mistakes to Avoid
Assuming @mentions grant access - They don't in confidential projects; only administrators can add users
Forgetting to plan team composition - Adding collaborators after project start causes workflow delays
Expecting automatic library updates - Responses must be manually added to libraries in confidential projects
Looking for confidential data in reports - Analytics deliberately exclude confidential project information for security
Need Help?
💬 Live Chat: Available in-app
📧 Email: [email protected] or contact your Success Manager directly for urgent support.
📚 Learning Centre: learn.autorfp.ai/en