Skip to main content
Relationships make connections explicit. A client can have several projects; a project can involve several people. Linking records helps your team follow those connections without maintaining the same details in multiple places.

​
Choose the kind of connection

Kato provides Record attributes for linking items and Relationship attributes for a paired connection between objects. A relationship can have a corresponding attribute on the other side, such as a project’s Client and a client’s Projects.

​
Decide how many records can connect

These are design examples. Choose the pattern that matches your team’s rules, then configure the relationship and the objects it connects.

​
Example: connect Projects to Clients

For this example, each project has one client and a client can have several projects. Start from the Projects object, so the pattern is many projects to one client.
  1. Confirm that both objects exist and that you can edit their attributes.
  2. In Projects’ Attributes settings, choose Create attribute, then select Relationship as the type.
  3. Name the Projects-side attribute Client.
  4. Choose Clients as the related object and select Many to one from the relationship options. Read the preview to confirm the direction.
  5. Name the corresponding attribute on Clients Projects, then save the configuration.
  6. Open the Relio website project and link its Client attribute to Relio.
  7. Open Relio and inspect the corresponding Projects relationship. Check that the website project appears there.
The names are from the perspective of each object: a project has a Client; a client has Projects. Using the same vague label on both sides makes the connection harder to interpret. Test with two projects linked to Relio. Both should fit the example’s model. If your business allows several clients on one project, that is a different rule: review a many-to-many relationship instead of forcing extra client names into a text attribute. Changing which records are linked is different from changing the relationship definition. The first changes one item’s connections; the second changes the structure used by the objects.
  • The expected object is not available: check the configured target object or allowed object types for the attribute.
  • Only one linked record is allowed: inspect the relationship’s one/many setting for that side.
  • There is no corresponding link on the other object: confirm that you created a paired Relationship, rather than assuming a Record attribute has the same reciprocal behavior.
  • Two similarly named records appear: inspect them before linking; display names alone do not prove that records represent the same item.
Use names that explain each side of the connection. Client and Projects are easier to follow than Related item on both sides. When adding a link, select the existing record that represents the item. Test the structure with a few examples. Confirm that each side allows the number of connections you expect before using it across the workspace.

Create focused views

Put the right records in front of your team.