✨ Special Offer! Get 40% Off Today with Code: GET40(40% OFF)

Odoo · Odoo-v19

How can a user enable or disable onboarding tours?

By PracticeTestSoftware Editorial Team6 min read
Question 7

Options

  • A Through the Settings app, under User Preferences, by turning the Show Onboarding Tips option on or off.
  • B From the user menu, select Preferences > Interface Options, and uncheck Display Onboarding Tours.
  • C Activate Developer Mode, open the debug menu, then toggle the Onboarding option, or click "Stop Tour" on the tour pop-up. ✓ Correct
✓ Correct Answer: C

Activate Developer Mode, open the debug menu, then toggle the Onboarding option, or click "Stop Tour" on the tour pop-up.

📖 Core Concept

Onboarding tours in Odoo are interactive guided walkthroughs designed to help users learn how to navigate and utilize specific features within the application. These tours appear as sequential pop-up tooltips that highlight interface elements and explain key workflows step by step. They are particularly valuable for new users who are unfamiliar with Odoo's interface or for existing users exploring newly installed applications.

The onboarding experience is contextual, meaning tours are triggered when users access specific modules or features for the first time. These guided experiences help reduce the learning curve and improve user adoption by providing just-in-time training without requiring separate documentation or training sessions. However, experienced users or administrators testing configurations may find these tours disruptive to their workflow.

Developer Mode in Odoo unlocks advanced functionality and debugging capabilities that are hidden from standard users to maintain interface simplicity. Among these capabilities is the ability to control onboarding tours globally or for specific contexts. This access level allows functional consultants and administrators to manage the user experience more granularly during implementation, testing, and training phases.

🔍 Detailed Explanation

Onboarding tours cannot be controlled through standard user preference settings available to regular users. Instead, their management requires access to Developer Mode, which is a special interface state that exposes technical features, debugging tools, and administrative controls not visible in the standard interface. Developer Mode is activated through the Settings menu or by adding specific parameters to the URL.

Once Developer Mode is active, the debug menu becomes accessible. This menu, represented by a bug icon in the interface header, provides numerous technical options including tour management. Within the debug menu, users will find controls specifically designed to start, stop, or disable onboarding tours. The "Onboarding" toggle allows users to enable or disable tours globally for their current session.

Additionally, when an onboarding tour is actively running and displaying its sequential pop-ups, users have the option to stop the tour immediately by clicking a "Stop Tour" button that appears within the tour interface itself. This provides an escape mechanism for users who want to exit a tour mid-way through without completing it. Stopping a tour in this manner typically marks it as completed or dismissed, preventing it from automatically restarting on subsequent visits to the same feature.

✅ Why the Correct Answer is Correct

Option C accurately describes the required workflow for managing onboarding tours in Odoo. Activating Developer Mode is a prerequisite because tour controls are not exposed in the standard user interface. This design decision prevents ordinary users from accidentally disabling helpful onboarding experiences while giving technical users and administrators the flexibility they need.

The debug menu, accessible only after Developer Mode is enabled, contains the Onboarding toggle that controls tour behavior. This toggle provides session-level control over whether tours should launch automatically. The option to click "Stop Tour" on the active tour pop-up provides an immediate escape mechanism that works even during tour execution.

This approach balances user experience goals with administrative flexibility. New users benefit from automatic tours, while power users and consultants can disable them when they interfere with configuration work or testing activities. The requirement for Developer Mode ensures that tour disabling is an intentional administrative action rather than an accidental user preference change.

❌ Why the Other Options are Incorrect

Option A

This option describes a pathway that does not exist in Odoo's user preference structure. While the Settings app does contain various user-related configurations, there is no "Show Onboarding Tips" option under User Preferences. User preferences in Odoo typically cover localization settings, notification preferences, and interface customizations, but tour management is not included among these standard settings. This reflects Odoo's design philosophy of keeping tour experiences automatic for standard users.

Option B

This option references a non-existent menu path. While users can access their preferences through the user menu, there is no "Interface Options" section that contains a "Display Onboarding Tours" checkbox. The user preferences interface focuses on language, timezone, email signature, and similar personal settings rather than tutorial or onboarding controls. This fictional pathway might seem plausible but does not correspond to actual Odoo functionality.

🔑 Key Terms
Onboarding Tours Developer Mode Debug Menu Tour Pop-up Session-level Control Guided Walkthroughs Interactive Tutorials
💡 Practical Example

Functional Consultant Configuration Workflow

A functional consultant is configuring the Sales module in a new Odoo implementation. Each time they navigate to the Sales dashboard to verify quotation workflows, an onboarding tour automatically launches, explaining basic sales processes. While valuable for end users, this interrupts the consultant's configuration work.

The consultant activates Developer Mode by navigating to Settings > General Settings > Developer Tools and clicking "Activate the developer mode." Once activated, a bug icon appears in the navigation bar. Clicking this icon reveals the debug menu, where the consultant finds and toggles the "Onboarding" option to disable tours.

Later, when preparing for user training sessions, the consultant wants to ensure the onboarding tour plays for the sales team. They re-enable onboarding through the same debug menu toggle. During a training demonstration, when a tour starts playing, one participant asks whether tours can be skipped. The consultant demonstrates clicking the "Stop Tour" button that appears on the tour pop-up itself, showing how users can exit tours if they prefer self-directed exploration.

⚠️ Common Mistakes
  • Looking for tour controls in standard user preferences where they are not available
  • Attempting to disable tours without first activating Developer Mode
  • Confusing tour management with general notification or tip settings
  • Assuming that stopping a tour once will prevent it from appearing for other users
  • Not realizing that tour settings may be session-specific rather than permanent user preferences
  • Expecting a dedicated Tours or Training section in the Settings application
  • Believing that tour availability can be controlled through access rights or security groups
  • Forgetting that the debug menu is only visible when Developer Mode is active
🎯 Exam Tips
  • Remember that onboarding tour management requires Developer Mode activation as a prerequisite.
  • Know that the debug menu, not user preferences, contains tour controls.
  • Recognize that there are two methods mentioned: toggling in the debug menu or clicking "Stop Tour" on the active pop-up.
  • Understand that tour management is intentionally hidden from standard users to preserve the onboarding experience.
  • Be aware that fictional menu paths in incorrect options may sound plausible but don't exist in actual Odoo navigation.