When you connect elements in Layer through a relationship, you are required to determine relationship cardinality: how many of one thing can be linked to another? This article will walk you through setting up those controls in Layer. For example: whether a room can contain many pieces of furniture, or whether a specific chair model can only be linked to a single vendor.

Getting cardinality right matters because it reflects real-world constraints and prevents invalid or confusing connections.

For example, when creating Room Data Sheets, each room has multiple pieces of furniture. But each piece of furniture only belongs to one room, but could have only one, or many vendors depending on how your team handles procurement. Layer gives you the flexibility to make those decisions yourself so that our tools match how you work.

In Layer, these rules are set directly through relationship field configuration. Want to learn more about Relationships in Layer? View our Layer Maker video on Relationships →

How to set relationship cardinality in Layer

First, you need to determine what type of relationship you are creating.

One to One: A one to one relationship means each element can be linked to only one corresponding element on the other side.

Example: Each RFI is linked to one specific drawing sheet, and each drawing sheet reference in that context points to only that RFI.

One to Many: A one to many relationship means one element can be linked to multiple elements, while each of those elements belongs to only one parent.

Example: One room can contain many pieces of furniture, but each furniture item is assigned to only one room.

Many to Many: A many to many relationship means multiple elements on both sides can be linked to each other without restriction.

Example: A furniture item can be associated with multiple vendors, and a single vendor can supply multiple furniture items across a project.

Once you know the real-world rules you are trying to model, the next step is configuring those rules in Layer. You can find them under the Relationship Field Settings under “Selection Mode”.

Common configuration issues

Most cardinality issues come from constraining the wrong side of the relationship.

[Screenshot: Example of incorrect category ownership]

This often happens when a relationship field is created on a parent category instead of a child category, or when a one-to-one selection mode is used where one-to-many behavior was intended.

When relationships behave unexpectedly, checking Selection mode and confirming which category owns the field usually resolves the issue quickly.

Changing cardinality on existing relationships

Selection mode can be changed after relationships already exist.

When changing cardinality on active data, review existing relationships to ensure the new limits align with expected usage.