Properties
Properties define the information stored on a record. Workstation presents native fields and custom fields in one place so administrators can manage labels, groups, validation, conditional behavior, formulas, usage, and data quality consistently.
Open Settings → Properties, then choose an object from Select an object.
Supported objects
Section titled “Supported objects”The Properties screen currently includes:
- Contacts, Accounts, Deals, Tickets, Projects, Activities, Appointments, Requests, Price Offers, and Invoices
- Campaigns, Articles, Products, Product Variants, Carts, Orders, and Line Items
- Ad Campaigns, Ad Sets, Ads, and Inbox Conversations
The available fields and options change with the selected object.
Property types
Section titled “Property types”System properties
Section titled “System properties”System properties are native Workstation fields such as Deal name, Pipeline, Stage, or Contact email. Their values stay in the record’s main data model.
You can change a system property’s display label, description, group, required setting, and supported validation rules for the workspace. Its internal name and field type remain locked because application features depend on them.
Custom properties
Section titled “Custom properties”Custom properties store organization-specific data. When creating one, set:
- Property label and optional description
- Object type and property group
- Internal name used by APIs, reports, filters, and automation
- Field type, options, default value, and validation rules
The internal name is generated from the label and can be adjusted before creation. It cannot be changed afterward. Pick a stable name that describes the data rather than a temporary business process.
Available custom field types include single-line text, multi-line text, phone, checkbox, multiple choice, date, dropdown, number, currency, file, Repzo user, URL, and email.
Computed properties
Section titled “Computed properties”Computed properties are read-only values calculated from other data. They do not store a manually entered value.
Workstation supports:
- Calculations using property references, arithmetic, comparisons, and functions such as
if,is_known,min,max,round, andconcat - Rollups that count, sum, average, find a minimum, or find a maximum across supported associated records
- Optional rolling time windows in days, weeks, months, or years
Use Test formula with sample values before saving a calculation. For Contacts, Add computed properties can install the standard Insights group when it is not already present.
Property tabs
Section titled “Property tabs”Properties
Section titled “Properties”The main table combines active system, custom, and integration-created properties. Search or filter by type, group, or creator. The table also shows where a custom property is used and its fill rate.
Select a row to review its details, rules, formula, preview, usage, and data quality.
Conditional logic
Section titled “Conditional logic”Conditional logic changes what happens when a controlling property matches a condition. A rule can:
- Show one or more dependent fields
- Show and require dependent fields
- Set a dependent value, either always or only when it is empty
Rules support conditions such as is any of, starts with, ends with, contains, and is known, depending on the controlling field type. When Stage is the controlling property, filter stage options by pipeline before selecting values.
Rules run from top to bottom. If more than one rule sets the same property, the lower matching rule wins. Active rules are enforced when supported records are created or updated; the form behavior is an aid, not the only validation layer.
Groups
Section titled “Groups”Groups organize properties in Settings and property pickers. Create, rename, reorder, or remove custom groups from the Groups tab.
A property’s group is administrative metadata. Moving a property into a group does not place it on a record-page card. Use Objects to control record-page placement.
Archived
Section titled “Archived”Archive a custom property when it should no longer be used but its definition may need to be restored. Archived properties move to the Archived tab.
Deleting a custom property is permanent and removes saved values. Review the Usage panel before archiving or deleting a property.
Validation rules
Section titled “Validation rules”The Rules panel always includes a Required option and adds checks based on field type:
| Field type | Available examples |
|---|---|
| Text | Minimum/maximum length, whitespace rules, regular expression, uniqueness |
| Number and currency | Minimum/maximum value, decimal places, uniqueness |
| Phone | Default country code |
| Date | Future only, past only, weekdays only, or a specific range |
| Multiple choice | Minimum and maximum selections |
Rules apply to native and custom properties. See Data Validation for choosing between always-on rules, conditional logic, and pipeline-stage requirements.
Usage and data quality
Section titled “Usage and data quality”The Usage panel shows references from forms, workflows, validations, conditional logic, formulas, and integrations. Check it before changing or removing a property.
The Data quality panel shows fill rate, clean values, detected formatting or validation issues, and sample records that need cleanup. Large datasets may be sampled to keep the scan responsive.
Using properties on record pages
Section titled “Using properties on record pages”Creating a property does not guarantee that it appears in a particular card. Go to Settings → Objects, edit the object’s default view, and add the property to a left-sidebar or middle-column property card.
See Objects for layout behavior and CRM Setup for the recommended configuration order.