Relio’s data model

How Hubs, Entries, Signals, Links, Lists and Views fit together — and how to decide which one a piece of information belongs in.

7 min

Every CRM has a model of your business underneath. Most hide it and make you live with theirs. Relio lets you shape it, so it is worth ten minutes to understand the pieces. Get them right and everything else — filters, boards, automation, AI — works with you instead of against you.

The pieces

Hubs are kinds of things. People is a Hub; so are Companies and Deals. A Hub defines what every item in it looks like.

Entries are the things themselves. Sara Ali is an Entry in People; Acme is an Entry in Companies. Every Entry belongs to exactly one Hub.

Signals are the details a Hub records about each Entry: a Person's email and job title, a Deal's value and expected close. Each Signal has a type — email, currency, date, a choice from a set — so Relio can check it, sort by it and add it up.

Links connect Entries in different Hubs. A Person has a Company; a Company has a Team. That is one Link, read from both ends: set it on Sara and it appears on Acme at once.

Lists follow a process. A Sales Pipeline List holds Deals; a Customer Onboarding List holds Companies. A List adds its own Signals — a Stage, a Kickoff date — that belong to the process, not to the Entry.

Views are saved ways of looking at a Hub or a List: which Entries (filters), in what order (sort), with which columns, as a table or a board.

A worked example

Imagine a property agency in Riyadh.

  • It needs People (buyers, owners) and Companies (developers) — both come with Relio.
  • It tracks properties, so an admin adds a Properties Hub with Signals like *District*, *Asking price* (currency, SAR), *Bedrooms* (integer) and *Listed on* (date).
  • Each Property has an owner, so the admin adds a Link from Properties to People: *Owner* on one side, *Properties* on the other.
  • Selling a property is a process, so the team creates a Sales List over Properties with a *Stage* — Listed, Viewing, Offer, Sold.
  • Each agent saves a View of the Sales List: *My properties*, filtered to themselves, shown as a board.

Nothing was copied. The Property lives once in its Hub; the List and the View are ways of working with it.

Hub or List? Signal or List Signal?

This is the decision people get wrong most often. Two questions settle it.

Is it a kind of thing, or a stage something passes through? A Property is a thing — a Hub. "Being sold" is a process — a List. If you catch yourself creating a Hub called *Leads* or *Renewals*, it is almost always a List over People, Companies or Deals.

Is the detail true of the Entry everywhere, or only inside one process? A company's industry is true everywhere — a Signal on Companies. Its *onboarding stage* only means something during onboarding — a Signal on the Customer Onboarding List.

HubList
RepresentsA kind of thingA process over things
An Entry isCreated in itAdded to it, from its Hub
Removing an EntryDeletes itTakes it off the List; it stays in its Hub
Its SignalsDescribe the EntryDescribe the Entry's place in the process
ExamplesPeople, Companies, Deals, PropertiesSales Pipeline, Onboarding, Renewals, Event Attendees

How the rest of Relio uses the model

  • Filters and Views work on Signals, Links and List membership — "Companies in Riyadh that have an open Deal and are not on Renewals".
  • Flows start when an Entry is created or a Signal changes, and act on Entries — create a Task, update a Signal, add to a List. See Flows.
  • Relio AI reads the same model. AI Signals are ordinary Signals that Relio AI fills in, so you can filter and sort by them. Ask Relio answers questions by building the same kind of filters you would.
  • Permissions can hide a Hub or a single Signal from someone; hidden Signals disappear from their tables, filters and AI answers alike.

Next

  • Hubs — the starter Hubs and creating your own.
  • Signals — every type and when to use it.
  • Lists — templates, boards and List Signals.

Checked against Relio on 29 October 2026