Custom Attributes

Custom Attributes let your workspace add extra fields to records such as leases, locations, and other subjects — fields that Leasecake does not include by default. Once configured, these fields appear on the record's form, detail view, and table, and they travel with the record through every workflow that touches it.

How Custom Attributes Work

Each attribute belongs to exactly one workspace and is scoped to one or more subject types — the kinds of records the field appears on. The Appears On filter in the attribute list shows which subject type a given attribute targets. Attributes are isolated per workspace: when a record is visible to more than one workspace, each workspace sees only its own attributes on that record.

Every attribute has a key — a stable identifier used by any integrations that post data to Leasecake. The key is derived automatically from the attribute's label when you leave it blank, and it stays the same even if you later rename the label. Because integrations reference the key rather than the label, editing a key breaks any integration already sending it.

Deleting an attribute frees its key immediately. If a new attribute is later created with the same label, it derives the same key — and any integration still sending that key will write into the new attribute. Treat deletion as permanent.

Managing Attributes in Setup

Open Setup in the left sidebar and select Custom Attributes. The list shows every attribute your workspace has configured, with columns for label, subject type, data type, and key. You can filter by Appears On (subject type) and by data type to narrow the list.

Creating an Attribute

Open Custom Attributes

Go to Setup > Custom Attributes and select New Custom Attribute.

Enter a label

Type the display name for the field. This is what users see on the record form and detail view.

Set the key (optional)

Leave the Key field blank to have Leasecake derive one from the label automatically. Enter a value manually only if an integration requires a specific key. The key must match the accepted format and must be unique within your workspace.

Choose the subject type

Select which kind of record this attribute appears on — for example, a lease contract or a location. This controls where the field is shown and which records it can hold values for.

Select a data type

Pick the type of value the field accepts (text, number, date, and so on). The data type cannot be changed after the attribute is saved.

Save

Select Save. The attribute is now active and will appear on the form, detail view, and table for the chosen subject type.

Reordering Attributes

The Reorder button appears in the attribute list only when the Appears On filter is set to a single subject type and no other filters are active. This restriction is intentional: reordering is scoped to one subject type at a time, so mixing filters would produce a partial and misleading result. To reorder, set the Appears On filter to the subject type you want to sort, clear any other active filters, and then select Reorder.

Where Attributes Appear

Once an attribute is configured for a subject type, it surfaces in three places on that record:

•Form — the attribute field appears in the editing form when creating or updating a record. Fields are grouped in a dedicated section.

•Detail view — the attribute and its current value are shown when viewing a record. Attributes with no value are hidden by default in multi-attribute sections; on dedicated custom-fields pages they remain visible with a placeholder so you can see every configured field.

•Table — a toggleable column and a matching filter are added to the record list. Both appear and disappear together depending on whether your workspace has any attributes configured for that subject.

Editing and Deleting Attributes

Select any attribute in the list to edit its label, key, or other settings. The key field is editable, but changing it will break integrations that reference the old key — update any connected systems before saving a key change.

To delete an attribute, open it and select Delete. Deletion removes the attribute and all values stored against it, and releases the key immediately. This action cannot be undone.

Attribute Keys and Integrations

When an external system posts data to a lease record using the `custom_fields` payload, each field is identified by its attribute key — not its label. This means:

•Renaming an attribute's label does not affect integrations — the key stays the same.

•Editing an attribute's key immediately breaks any integration sending the old key.

•If a key is left blank when saving, Leasecake derives one from the label. This derivation also runs as a repair pass — if a row was written without a key (for example, during a rolling deployment), the key is filled in automatically on the next save without changing the record's modification timestamp