Built LMS Help Center
Settings

Intelligence Settings

Configure the intelligence pipeline, automation mode, privacy mode, and alert verbosity.

Use Settings > Features > Intelligence to control how Learning Intelligence analyzes learner activity and how much action it can take from its findings.

For reading dashboards and insights, see Learning Intelligence. For pipeline diagnostics, see Configure Intelligence and Pipeline Health.

Before you begin

You need analytics-read permission to view this page and analytics-manage permission to change settings.

Before changing intelligence settings, decide:

  • Whether the pipeline should run.
  • Whether analysis should refresh daily or weekly.
  • Whether the system should only recommend, suggest actions for approval, or act automatically.
  • How much learner identity should be visible.
  • How noisy alerts should be.

These settings affect how admins and managers interpret learner mastery, recommendations, alerts, and automated actions.

Review intelligence controls

What the page controls

The page has four setting groups:

GroupUse
Intelligence PipelineEnable analysis and choose daily or weekly refresh.
Automation ModeChoose how the system acts on findings.
Privacy ModeChoose whether learner identity appears at individual, team, or anonymous level.
Alert VerbosityChoose quiet, normal, or verbose alert volume.

Each setting saves when changed.

Configure intelligence behavior

Configure the intelligence pipeline

Turn on Enable Pipeline when Built LMS should run scheduled analysis to compute mastery scores, health metrics, and insights.

When the pipeline is disabled, existing intelligence data is preserved, but new analysis does not run.

Choose a schedule:

ScheduleUse it when
DailyLearner activity changes often and teams need current insights.
WeeklyActivity volume is lower or weekly review is enough.

If dashboards look stale, check whether the pipeline is disabled or scheduled less often than expected.

Choose automation mode

Automation mode controls what the intelligence system can do with its findings.

ModeBehavior
Recommend OnlyShows insights in dashboards. No automated actions.
Suggest with ApprovalProposes actions such as enrollments or nudges that admins approve before execution.
Fully AutomatedExecutes recommended actions automatically, such as auto-enrollment or auto-nudges.

Use Recommend Only when first rolling out intelligence or when admins want full control. Use Suggest with Approval when you want help finding actions but still need human review. Use Fully Automated only when the organization has validated the recommendations and is comfortable with automatic actions.

Choose privacy mode

Privacy mode controls how learner identity appears in mastery dashboards, TIL feeds, and analytics.

ModeBehavior
IndividualFull learner names are visible. Managers see their direct reports.
Team AggregatesMastery data appears at group level with no individual drill-down.
AnonymousLearner identities are anonymized across dashboards and feeds.

Choose the least-identifying mode that still supports the decisions admins and managers need to make.

Choose alert verbosity

Alert verbosity controls how many intelligence alerts are generated.

LevelBehavior
QuietCritical alerts only, such as major skill regressions.
NormalStandard alerts for anomalies, gaps, and milestones.
VerboseAll alerts, including minor trends and incremental changes.

Use Quiet for executive or low-noise environments. Use Verbose only when someone is actively monitoring the signal and wants detail.

Roll out intelligence safely

For a new organization or a team using intelligence for the first time:

  1. Enable the intelligence pipeline.
  2. Start with a weekly schedule if learner volume is low, or daily if the team reviews insights every day.
  3. Set automation mode to Recommend Only.
  4. Set privacy mode to the least-identifying option that still supports the team's workflow.
  5. Set alert verbosity to Normal.
  6. Review dashboards for at least one cycle before approving automated actions.

Move to Suggest with Approval only after admins trust the recommendations. Use Fully Automated after the organization has a clear policy for automatic enrollments, nudges, or other actions.

Review settings after a policy change

Review this page when:

  • Managers gain or lose access to learner-level data.
  • The organization changes privacy expectations.
  • Admins complain that alerts are too noisy or too quiet.
  • Automated recommendations are being approved without much review.
  • Intelligence dashboards look stale after a launch or large enrollment change.

Verify and support intelligence settings

Verify success

After changing settings:

  • The setting updates without an error.
  • Pipeline status and schedule match the intended operating model.
  • Automation mode matches your approval policy.
  • Privacy mode matches internal data visibility expectations.
  • Alert volume changes match the selected verbosity level.

Troubleshooting

On this page