Skip to main content
An object describes a kind of thing your team tracks. Clients, projects, and people are examples. Each object has its own attributes and a collection of records that use those attributes.

Open an object

Find your workspace’s objects in the Objects section of the sidebar. The names depend on how your workspace is configured. Open one to browse its records and the available views.

Decide whether you need a new object

Create an object when you need a separate collection with its own details and connections. A team that manages properties, for example, might need a Properties object with an address and links to the people responsible for each property. If you only need another detail about an existing item, add an attribute instead. If you need to focus on a subset of the same items, create a view.

Sketch the object before creating it

Write down three real examples of what the object will contain. For Projects, these might be Relio website, Relio onboarding, and Harbor brand refresh. Then identify the information that all three need. If your examples need unrelated sets of attributes, you may be combining two kinds of thing. If two proposed objects need the same details and differ only by status, one object with separate views may be easier to maintain.

Create and check the structure

When you have access to object configuration, open the object creation form. Fill in its name and singular/plural labels, add a short description, and choose an icon. After creation, review its Attributes settings and add the custom details you need. Existing system attributes may already cover some details. Create one sample record before adding all your data. Check whether its form asks for the right information and whether another teammate can understand the record without an explanation from you. If you cannot find the configuration controls, ask your workspace administrator to review the object with you. Do not create a substitute object solely to work around an access problem.

Name it for your team

The object creation form includes a name, singular and plural labels, an icon, and a description. Use names your teammates recognize: Property for one record, Properties for the collection. A short description can explain what belongs here. Before expanding the structure, add a few representative records. Check that the attributes capture the information you need without making everyday entry cumbersome.

Design useful attributes

Choose the details each record should hold.