The embedded terminal is the primary interface between MyQ and your users at the device. The look and feel of the terminal, including available actions, labels, ordering, icons, and colors, is highly configurable. A well-designed terminal experience can reduce training overhead, speed up device interactions, and help improve consistency across the device fleet.
Terminal experience design depends on group configuration (which users see which actions), authentication configuration (what the login screen looks like and how it behaves), and branding decisions (logos, colors, action names) that may involve stakeholders outside the IT team. Build it into your deployment timeline accordingly.
Terminal Actions
Terminal actions are the workflows available to authenticated users on the device panel – Easy Scan destinations, Easy Copy presets, access to device-native applications, ID card registration, and others. Terminal actions can be scoped to specific users or groups, ordered and organized into folders, and labelled in user-friendly language.
The key design decisions before go-live are:
-
Which actions does each user population need?
Map actions to groups as part of your group design process – the two are interdependent. -
What should each action be called?
Default action names may not match the language that users expect. Use names that describe the task clearly, for example, "Scan to HR SharePoint" instead of "Easy Scan 3". -
How should actions be ordered?
Frequently used actions should appear first. Consider whether folders are needed for users with many available actions, or whether a flat list is cleaner for users with only two or three. -
Which actions should users be able to add to their Favorites?
Users can designate personal favorite actions for faster access. If this is enabled by default for your terminal package, make users aware of it during onboarding.
Branding and Custom Themes
MyQ supports visual customization of embedded terminals, including terminal themes and custom appearance for terminal actions. For organizations deploying across a multi-vendor fleet, consistent naming, icons, colors, and themes can help make the experience more predictable, even where terminal behavior differs by vendor or package.
Branding decisions, such as logo files, color choices, icons, and theme selection, should be planned before terminal configuration and may require input from your marketing or communications team.
See also: