Skip to main content

Introduction to Settings - Article

Understand the platform’s shared settings, configuration responsibilities and dependencies, including recommendations, appearance, AI availability, security and integrations.
Updated: 30 Oct 2026
6 min read

Summary

Settings is the shared configuration foundation for the platform. It connects identity, access, communication, discovery, presentation and integrations so that individual courses and activities can operate within a coherent organizational model.

Treat configuration as a governed service, not a collection of unrelated switches. Different roles and enabled modules expose different controls, and a change can affect many users, Organizations, courses or automated processes.

Use this article to:

  • Understand the purpose of the main Settings areas
  • Identify the right owner and configuration layer
  • Distinguish global defaults from activity and content decisions
  • Plan, test and communicate changes safely

The Control Layer of the Platform

The Settings area holds the platform’s shared configuration. Features such as Commerce, Skills, Incentives, discovery and AI have their own working experiences, while Settings establishes important defaults, availability and integrations behind them.

Access depends on the user’s role, permissions, enabled modules and the particular configuration area. Global Administrators and Platform Administrators maintain many organization-wide settings; some technical AI, provider or integration controls are restricted to an Administrator or maintained by Eurekos. Do not assume that every role with a Settings menu sees every tab or field.

Use the narrowest appropriate configuration responsibility and involve the platform owner when a change affects security, integrations, automation or a broad user population. A staff member who authors learning content does not need unrestricted platform settings simply to maintain a course.

Shared changes can affect many users, automation, communication and security. Keep a named owner, understand dependencies and verify the actual outcome before expanding a change.

Why Settings Matters

Many parts of the user experience are shaped by decisions made in Settings.

For example, when a learner logs in and only sees specific courses in the storefront, that visibility is not random — it is controlled by roles, groups, onboarding rules, and tagging configurations defined in Settings.

When an instructor can be scheduled for a training session, that ability depends on how roles, permissions, and skills have been configured.

When an automated email is sent about a new enrollment, or when incentives award points for completing a certification, those behaviors are also governed centrally.

Even security — such as password policies, authentication methods, and two-factor authentication — originates here.

In short, Settings determines who can access what, how the platform behaves, and how it aligns with your operational and compliance requirements. Many system-wide behaviors depend on choices made in this area, while individual activities and content retain their own configuration. If the User Profile is the operational junction of people, then Settings is the structural foundation beneath it.

Below is a short purpose-driven overview of each category currently available in the Settings menu.

Settings AreaPurpose & What It Covers
GeneralDefines global platform behavior and foundational feature toggles. Includes activation of core modules (e.g., Skills, Availability), system-wide configuration settings, and privacy/legal-related controls. Typically one of the first areas configured during implementation
Email SendingControls how the platform communicates. Includes SMTP configuration, system notification handling, email template management, privacy policy distribution controls, and test mode options. Impacts enrollments, certificates, incentives, compliance emails, and overall user communication
TagsManages taxonomies and vocabularies used across the platform. Tags categorize courses and activities, drive filtering and reporting, populate user Interests automatically, and support onboarding logic. Tag structure directly affects discoverability, segmentation, and automation
TranslationsEnables multilingual support. Includes interface text customization, email translations, legal content translations, and language activation. Critical for global deployments and extended enterprise environments
AppearanceDefines logos, colors, fonts, banners and interface styling. The Recommendations tab controls the carousel’s presentation; it does not select the slide content. See Appearance and Configure the Recommendations Carousel Appearance.
CommerceConfigures monetization and order workflows. Includes payment providers, checkout logic, pricing models, VAT handling, and order management. Directly impacts storefront functionality and paid training workflows
SecurityManages platform-level security standards. Includes authentication policies, password requirements, access configuration, and enforcement controls. Foundational for protecting personal data, intellectual property, and regulated information
SkillsDefines structured competency tracking. Includes skill creation and management. Powers readiness validation, instructor scheduling, certification logic, and partner enablement models
Third Party IntegrationsConnects external identity, file, meeting, commerce and other supported services. Artificial intelligence (AI) configuration is also reached here where enabled. Availability, providers and content indexing are separate decisions; see Configure Saga Availability and Access.
RolesDefines naming, labeling, and translation of standard user roles. Supports organizational clarity and localization without changing underlying permission logic
Regional and LanguageControls localization settings. Includes time zones, date formats, and language management. Impacts reporting, certificates, transcripts, and system-wide formatting
Page TemplatesMaintains single-page starting designs for supported page types. Templates can contain guidance, sections and styling, or be largely empty apart from protected elements. A reusable full Course structure is maintained as a source/template Course, not created by one page template
FormsManages configurable fields across the platform. Includes profile form fields, user creation form, contact forms, and visibility controls. Directly impacts user profiles, onboarding automation, reporting, and segmentation
Analytics PermissionsControls reporting access and data visibility. Defines which roles can access specific analytics types. Critical for governance, hierarchy, and controlled data exposure
OnboardingConfigures automated assignment logic. Enables auto-enrollment rules based on role, organization, tags, or profile attributes. Connects user data with automated training workflows
LinksManages footer and sidebar links. Includes Terms of Use, Privacy Policy, contact information, cookies, accessibility reports, and custom links with role-based visibility controls. Supports governance and structured navigation
IncentivesControls the full incentives ecosystem. Includes point rules, badges, expiry schedules, shop configuration, products, and transaction handling. Drives engagement and reward-based learning programs
StorefrontConfigures public-facing catalog behavior. Controls visual presentation, content visibility logic, and the experience for both registered and unregistered users
RecommendationsChooses and orders the My Overview slide plan: Last visited, In progress, Personalized recommendations, Bookmarked and Custom offers. Each learner sees only applicable items. See Configure Recommendations on My Overview.

Choose the correct configuration layer

DecisionWhere it belongs
Which users receive Saga?AI availability under Third Party Integrations; this does not grant access to every course.
Which offers appear in the dashboard carousel?Recommendations for slide selection and order; the learner’s eligibility still applies.
How should those slides look?Appearance → Recommendations for layout, timing and overlay.
Which training is Mandatory or has an enrollment deadline?The relevant Training Activity configuration, not a branding or recommendation setting.
Which page layout starts new content?Page Templates for a single-page starting design; a structured template course is a separate reusable source.

Plan and verify a settings change

State the intended outcome and affected population before changing a shared setting. Record the current value, dependencies and any Organization override. Use a non-sensitive example and a representative learner or staff account to check the actual outcome, not only whether the setting saved.

For a carousel change, verify a new learner and a returning learner. For AI availability, verify an included and excluded Organization. For branding, check several screens, long titles and relevant exports. Apply only the intended change and communicate any operational effect to the people maintaining courses and activities.

Troubleshooting

ProblemWhat to check
A setting described in an article is absentCheck role permissions, optional module activation and the configuration owner. Some technical setup is maintained by Eurekos.
A global change has an unexpected local resultInspect Organization overrides, feature-specific controls and the source record before assuming the global setting failed.
A recommendation is mistaken for assigned trainingRecommendations promote eligible offers. Mandatory status, assignment and enrollment are separate activity workflows.
A change saved but the expected output has not refreshedCheck the feature’s processing model. Indexing and overnight recommendations are not necessarily immediate.

FAQ