I'm submitting this enhancement request on behalf of our strategic client, Microsoft.
Problem Statement
Microsoft has identified a need to prevent certain internal documents, specifically instructional or SOP (Standard Operating Procedure) process documents, from being used by Responsive AI (Ask, AI Assistant, and AI Draft) when generating responses.
Currently, all eligible Content Library documents and Q&A pairs are automatically considered in AI searches and response generation. This creates a risk of AI leveraging internal procedural documentation or non-client-facing materials that are not intended for use in proposals or external communications.
The lack of an exclusion mechanism limits administrative control and can compromise content relevance and compliance with internal communication standards.
Proposed Enhancement
Introduce the ability to exclude specific Content Library records (documents and Q&A pairs) from AI searches and AI response generation.
Preferred functionality (in order of priority):
- Record-level control: Add a checkbox within each Content Library record’s metadata — e.g., “Exclude from AI Searches.” When checked, this record would be ignored by all AI-driven functions (AI Assistant, AI Draft, Ask, etc.).
- Bulk exclusion option: Allow administrators to select multiple Content Library records and apply the “Exclude from AI Searches” setting in bulk, improving efficiency for large-scale management.
- Organization-level configuration (optional alternative): Within Organization Settings > Responsive AI > Preferences, provide an option for administrators to exclude entire collections or content tagged with specific labels from AI consideration.
Business Impact
- Improved content governance: Ensures AI-generated responses align with approved, client-facing materials.
- Reduced compliance risk: Prevents internal or confidential SOPs from being surfaced in proposals or client interactions.
- Administrative efficiency: Provides simple, scalable controls to manage AI content inclusion at both record and organizational levels.
@Gosia Rios for visibility.
