Conversation
src/System Application/App/AI/src/Copilot/CopilotAICapabilities.Page.al
Outdated
Show resolved
Hide resolved
src/System Application/App/AI/src/Copilot/CopilotAICapabilities.Page.al
Outdated
Show resolved
Hide resolved
src/System Application/App/AI/src/Copilot/CopilotAICapabilities.Page.al
Outdated
Show resolved
Hide resolved
…s.Page.al Co-authored-by: Darrick <darjoo@users.noreply.github.com>
…s.Page.al Co-authored-by: Darrick <darjoo@users.noreply.github.com>
|
Does the data apply to across companies? We have some logic where we enable the privacy notice for evaluation companies, but if we build the metadata across all companies this could be an issue, as switching company would then mark the notice as disabled. As this is the object metadata and is across companies, we probably need to leave it disabled, even for eval companies. edit: alternatively, what is the difference between this and the AOAI privacy notice -- aren't we sending the data to the same place? |
When privacy notice is enabled, the approval is stored without any company identifier. This means privacy approval is applied across companies
AOAI privacy notice is conditional and only shown when AOAI services are not present in the region. The privacy notice for semantic search needs to be shown in all regions and hence we could not re-purpose AOAI privacy notice |
There is an edge case where the privacy notice is not set. When validated through Copilot capabilities the
I assume you will be able to follow the same logic, consent is only needed if you leave the current geo. Admins can still control the consent via the privacy notices page in any case. |
For now we're not using this codeunit to evaluate consent but yes, this needs to be fixed. |
Porting changes from Platform-Core PR #233155
Fixes AB#623789