Outbound data restrictions after searching data sources (#1106)

This commit is contained in:
Thorsten Sommer authored and GitHub committed 2026-10-23 09:27:22 +02:00
1 parent 7ba5f01388
commit 8c5cfa78b6
61 files changed
+1389 -143

No files matched your search

@@ -17,4 +17,15 @@ public sealed class DataSourceSecuritySettings(Expression<Func<Data, DataSourceS
/// Provider instance IDs trusted by an organization for data-source security checks.
/// </summary>
public HashSet<string> TrustedProviderIds { get; set; } = ManagedConfiguration.Register(configSelection, n => n.TrustedProviderIds, []);
/// <summary>
/// The least strict outbound data restriction a data source may have.
/// </summary>
/// <remarks>
/// Only an organization sets it; the default leaves every level to the user. A data source set to
/// a less strict level gets this one when its passages reach a chat, see
/// DataSourceOutboundDataExtensions.GetEffectiveOutboundDataRestriction, and its dialog no longer
/// offers the less strict levels.
/// </remarks>
public OutboundDataRestriction MinimumOutboundDataRestriction { get; set; } = ManagedConfiguration.Register(configSelection, n => n.MinimumOutboundDataRestriction, OutboundDataRestriction.UNRESTRICTED);
}