Change Management: Modules and Features | CLUE Learning

Use the change management settings to control which parts of CLUE your team can sees and how new features are rolled out. This helps organization administrators keep the system easier to use, test changes before a full rollout, and make sure the right people have the right access.

CLUE gives administrators control over what is available in the system and how it behaves for the organization. That includes turning modules on and off, changing feature settings, testing new tools in beta, and controlling access using roles and job titles. If you also need to control what each role can do, visit our Managing Job Titles and Understanding Permissions and Roles articles.

This article is mainly for people who handle the management, setup and rollout of features inside CLUE.

• System Administrators - control which modules and features are available to the organization
• IT Managers - test new tools first and plan rollouts before wider release
• Equipment Managers - stay aware of new features that may affect operations, reporting, or maintenance setup

How to Use It

Use these settings when you want to simplify the sidebar by displaying only certain links, control how features work for your organization, or test changes before they go live for everyone. We recommend starting with modules, then reviewing feature settings, beta access, and role permissions. The main administrator setup in CLUE lives under Admin > Company Settings, which is also where roles and other organization-level configurations are managed.

1. Enabling or Disabling Modules

Within your CLUE dashboard go to Organization > Modules.

Each module has a toggle which can be toggled on or off. We recommend turning off the modules your team does not use so they do not appear in the sidebar on the left side of the screen for users. This helps keep the interface cleaner, especially for field teams that only need a smaller part of CLUE. It can also help keep your team focused on the areas of CLUE which are important to the team and organization.

For example, if your team does not use a certain reporting or maintenance areas, you can turn that module off so it no longer shows in the sidebar. The CLUE sidebar groups tools into sections like Insights, Maintenance, Directory, and Admin, so turning off unused areas can help keep things organized and clean for your team.

2. Configuring Feature Behavior

Within your CLUE dashboard go to Organization > Features.

This is where you control how certain features behave inside each area of CLUE. Settings are usually grouped by product area, such as Dispatch, Equipment, Inspections, or Projects.

You can use this page to control things like:

• which dispatch notifications are available
• which equipment status options users can choose from
• which inspection template sets are available
• whether projects can be auto-detected from GPS locations

3. Test New Features on Beta First

CLUE releases new features to beta first. Use the beta environment to try out and test new features and changes before turning them on for the rest of your team.

This gives organization administrators time to review new or updated workflows, train their users, and decide whether the feature should be enabled broadly or start off conservatively. CLUE's learning pages also call out and highlight beta releases on newer features, so you can easily find and learn about them.

4. Control Permissions per Role

In order for you and your users to use CLUE as effectively as possible, it's important to understand that modules and feature settings control what is available and shown in the CLUE dashboard. On the other hand, roles and permissions control what each user is allowed to access and what actions they can perform within the CLUE dashboard.

You use Job Titles and Permissions to decide who can edit work orders, approve timecards, manage parts, or access admin features. If you need to review your organization setup before changing access, our Understanding Organization Structure article is also worth reviewing because structure affects visibility across the system.

Summary and Tips

A few simple habits can make change management much easier.

• Turn off modules your team does not use.
• Test new features in beta before rolling them out to your entire organization.
• Review your permissions often so roles still match real responsibilities.
• Keep the sidebar as simple as possible for field users.
• Check product updates regularly so changes do not surprise your team.
• If a new feature changes who should see what, review Managing Job Titles and Understanding Permissions and Roles at the same time instead of treating rollout and permissions as separate tasks.