Compliance Controls
Usage guidelines, privacy mode, and audit-relevant settings
This area defines the compliance baseline for productive usage.
Core functions
- audit log for security- and data-protection-relevant settings changes
- usage guidelines for acceptable user behavior
- mandatory onboarding/training components (see below)
- privacy/GDPR mode
- API logging mode
- DPA-related information
Mandatory onboarding/training components
Under Settings → Mandatory Trainings you define which trainings your members must complete in Learn & Discover. Pick from over 70 ready-made courses – from AI foundations to department-specific use cases – and mark the ones relevant to your organization as mandatory.
The Course settings on the same page control which actions learners can take. These settings apply workspace-wide to all courses, not only the ones marked as mandatory:
- Allow skipping lessons: when turned off, learners must complete every lesson instead of skipping it.
- Allow showing hints: when turned off, learners no longer see the hint or the sample solution.
Turn both off so learners complete the exercises themselves and the learning effect is preserved.
Lock behavior for outstanding mandatory courses
As long as a member has at least one assigned mandatory course still open, meinGPT shows a dialog listing the outstanding courses on every page outside the course pages themselves, and it cannot be closed - not with Escape, not by clicking outside it. The only way past it is to open one of the listed courses. This also affects internal areas such as the support ticket portal: they stay locked for that member until all mandatory courses are completed.
Outpost search log
Available once meinGPT has enabled Governance for your workspace. Find it under Settings → Knowledge & integrations → On-premise, via the Outpost search log button.
The log records every search against an Outpost knowledge pool: the question as it was asked, who asked it, which Outpost and pool were searched, and whether an answer came back.
Why in meinGPT and not on the Outpost. The search is sent from meinGPT — the Outpost only answers it. Keeping the log on the device would therefore not keep the query in the building, because it was never there, while putting it out of reach of the people who need to read it. With several Outposts it would also mean one console per device.
On-premise only. Searches against cloud knowledge collections are not recorded.
Retention: 90 days. Entries are deleted automatically after that; the window is also stated below the table.
Only from the moment you switch it on. The switch controls collection, not just the view: while Governance is off, nothing is stored. After switching it on, only searches made from then on appear.
Attention
Works-council agreement. In Germany a register of all employees' search queries is generally subject to co-determination (§ 87 (1) no. 6 BetrVG). Agree the rollout with the works council before asking meinGPT to enable the feature for your workspace.
Admin practice
- keep guidelines short and actionable
- choose privacy mode based on risk profile
- align mandatory training with rollout phases