Signals

Every Signal type and when to use it, creating and editing Signals, and the difference between hiding a column and changing a Hub.

7 min

A Signal is one piece of information that a Hub records about every Entry: an email, a stage, an amount, a date. In a table, each Signal is a column; in the preview, it is a row under Details.

Because every Signal has a type, Relio knows how to edit it, check it, filter it and add it up. Choosing the right type is the most useful decision you make when setting up a Hub.

Signal types

TypeUse it forFilter with
textShort text: a job title, a cityis, contains, starts with, ends with, is any of
long_textParagraphs: a description, backgroundcontains, does not contain
emailAn email address; checked when enteredas text — ends with finds a domain
phoneA phone numberas text
urlA web address, like a company's domainas text
number, integer, decimalCounts and measures; integer for whole numbersis, greater than, at least, less than, at most, between
currencyMoney, in one currency you choose, e.g. SARas numbers
percentageA share, like a deal's probabilityas numbers
date, datetimeA day, or a day and timeas numbers, plus before and after
booleanYes or nois, is not
selectOne choice from a set: Stage, Industryis, is not, is any of, is none of
multi_selectSeveral choices: Tags, Serviceshas, has any, has all
userA member of your workspace: Owner, Account manageris, is not, is any of
locationAn address or placeis empty, is not empty
ai_flag, ai_choice, ai_scoreFilled in by Relio AI. See AI Signalsas yes/no, choice and number

Every type can also be filtered with is empty and is not empty.

Every Hub also has Name, and Relio keeps Created — when the Entry was made — for you. You cannot edit Created, and it is never required or unique.

Creating a Signal

Only workspace admins can change a Hub's Signals.

  1. Open the Hub and click the Settings icon next to New Entry.
  2. Click Create Signal.
  3. Enter the Name, e.g. *Renewal date*.
  4. Optionally, set the API slug — the name used by integrations and the API. Relio makes one from the name; set it yourself if the name is in Arabic.
  5. Choose the Type. For currency, enter the three-letter currency code. For select and multi-select, enter the options one per line.
  6. Tick Required if every Entry must have a value, and Unique if no two Entries may share one.
  7. Click Save.
Creating a Signal
Name, type and rules for a new Signal.

The new Signal appears as a column in the table, empty for existing Entries.

Required and Unique

Required means a new Entry cannot be created without the value, and an existing value cannot be cleared. Entries created before you made it required keep working; fill them in as you go.

Unique means no two Entries in the Hub may have the same value — useful for email addresses or company domains. If existing Entries already share a value, Relio tells you which ones collide, and nothing changes until you fix them.

Editing a Signal

In the Signals dialog, click a Signal to rename it or change Required and Unique. Its type cannot be changed; create a new Signal of the type you need and move the values across — for example, select the Entries, Copy them, paste into a spreadsheet, and import it back matched on a unique Signal.

Renaming a Signal never breaks Views, filters or Flows — they refer to the Signal itself, not its name.

Hiding a column is not changing the Hub

The Signals button in the table's toolbar only chooses which columns *you* see in this table or View — anyone can use it, and it changes nothing for anyone else unless they save it into a View. The Settings icon changes the Hub itself, for everyone, and is for admins.

Signals on Lists

A List can have its own Signals, like *Stage* or *Kickoff date*, which belong to the process rather than the Entry. They are created the same way, from the List's Settings. See Lists.

Checked against Relio on 29 October 2026