Skip to main content

The Global Search

Learn here, how the global search works and how to get the best results

Written by Katharina Kos

Availability

Packages: All packages

User Roles: All user roles

Global Search lets you find anything across remberg from a single search bar: Assets, Work Orders, Work Requests, Tickets, Organizations, and Parts. Instead of navigating to individual modules, you enter your search term once and see all matching results in one place.


How to search

Type at least 3 characters into the search bar. Search runs across all object types in parallel and shows the best matches first.


What gets matched

You type…

Search looks at…

A name or title

Asset name, Work Order subject, Ticket subject, Organization name, Part name

A serial number or external reference

Asset ID / Part number, External Reference fields

A number like #1234 or 1234

Work Order, Work Request and Ticket IDs

Words from a description

Work Order, Work Request and Part descriptions

Words from a note

The Asset or Work Order the note is attached to

Words from a Ticket message

The Ticket the conversation belongs to

A custom property value

Custom fields on Assets, Work Orders, Tickets, and Parts


Finding linked content automatically

Search also thinks across connections: when you search for a contact, Organization, or Asset, it surfaces not just the object itself but everything linked to it.

Searching for a contact: Enter the contact's full first name, last name, email address, or external reference → Search also returns the Work Orders, Tickets, Assets and Organizations linked to that contact.

💡 Note: For linked objects to appear, you need to enter a complete value: the full first name, full last name, full email, or full external reference. Partial terms like "Han" for "Hans" won't pull in linked items.

Searching for an Organization: Enter an Organization's name → Search also returns its Assets, Work Orders, Tickets and Parts.

Searching for an Asset: Enter an Asset's name or ID → Search also returns Work Orders, Work Requests, Tickets and Parts that reference it - for Work Requests, this includes those on child machines.


Filters

Narrow your results by:

  • Type: show only Assets, Work Orders, Tickets, etc.

  • Created or Updated date: e.g. last 7 days, last 30 days


How results are ranked

Results are sorted by relevance first, then by most recently updated. The approximate order:

  1. Exact match on a number (#1234) or identifier (ID, external reference)

  2. Match on a name, subject, or label

  3. Match via a linked contact, Organization or Asset

  4. Match in a description, note or conversation


Tips for better results

  • Looking for a Work Order by number? Type # plus the number, or just the number on its own.

  • Can't find an Asset? Try its ID, partial matches work.

  • Want everything tied to a person? Type their full first or last name.

  • No results? Shorten your search term or clear any active date filters.


FAQ

How many characters do I need to type before search starts?

At least 3 characters. Search only activates once you've entered 2 or more characters.

Why aren't linked objects showing up when I search for a contact?

The cross-reference logic only works with complete values. "Han" isn't enough to reliably identify the contact "Hans Müller" and load their linked Work Orders or Tickets. Enter the full first name, last name, or email address.

Can I search across Tickets and Work Orders at the same time?

Yes. Search runs across all object types simultaneously by default. You can then use the Type filter to narrow down to a specific object type.

Are notes and Ticket messages included in search?

Yes. Words from notes are matched to the object the note is attached to (Asset or Work Order). Words from Ticket messages lead to the corresponding Ticket.

Why do some results appear higher than others?

Ranking follows relevance: exact matches on numbers or identifiers appear first, followed by name and subject matches. Matches via linked objects or from descriptions and notes appear further down.

Did this answer your question?