Hey Limble Community, Your friends on the Customer Success team are looking forward to this week’s Office Hours, and we'd love for you to join us! Think of this as an open forum to connect, share, and learn more about making Limble work best for you. In every session, you'll have the opportunity to: Ask Anything Limble:…
While assets in Limble have field-level change history available, complete with a visible history icon next to each field, parts do not have the same functionality. Most fields on parts have no history tracking at all, and even for those that do, there is no icon or direct access. Instead, users must open the general log…
Currently, logged-in users cannot see the full history of their own submitted work requests if those requests are tied to locations outside of their permission scope. To access a complete history, they must open an incognito browser session and search as if they were not logged in. This creates unnecessary friction and…
Users need the ability to reuse documents and images across multiple assets without uploading the same file multiple times. A shared document management system, similar to a lightweight SharePoint model, would reduce redundancy and streamline documentation efforts. Current Limitations Files must be uploaded separately to…
Currently, users cannot rename documents once they are uploaded into the system. This limitation affects organization, clarity, and usability—especially when documents are reused or linked across various records and assets. Current Limitations Uploaded files retain their original filenames, which are often unclear or…
Users frequently need to customize dropdown lists within instructions for specific tasks or processes. However, the current system lacks the ability to save a modified version of a dropdown list as a new instruction, forcing users to recreate instructions from scratch, even when only slight changes are needed. Current…
Managing asset imagery within Limble is currently a manual and inefficient process. Users often capture relevant photos while completing tasks, but there is no direct way to use those images to update an asset’s profile picture. This creates unnecessary steps and wastes time during asset documentation and update workflows.…
Currently, when part inventory levels dip below the minimum threshold, Limble automatically generates a reorder task, regardless of whether there are pending purchase orders (POs) that would soon replenish stock. This behavior can create unnecessary tasks and lead to confusion, particularly in workflows where parts are…
When users keep the Limble CMMS application open in a browser tab for extended periods, the system becomes stale or unresponsive—often requiring a manual refresh. In some cases, having multiple tabs open causes severe performance issues, significantly slowing down the user’s machine or rendering it temporarily inoperable.…
It looks like you're new here. Sign in or register to get started.