Customization

Customizing Company Properties

TL;DR

Company properties are custom fields that let you store additional company information beyond the standard fields. To add a custom property: go to Customize > Custom Fields > Company, click New Property, choose your data type (text, number, select, tags, etc.), set a label and unique identifier, configure validation rules, and save. You can then edit these properties directly in company list views and detail pages.

Introduction

Company properties extend your CRM's standard company object with custom fields tailored to your organization's needs. Instead of being limited to built-in fields like company name, website, and industry, you can capture any additional information relevant to your business—whether that's account tier, contract renewal date, number of employees, preferred contact method, or any other attribute.

These custom properties:

  • Are scoped to your entire tenant (organization)

  • Persist across the application's standard workflows

  • Support multiple data types (text, number, select, tags, and more)

  • Can be edited inline in company list views or in detail drawers

  • Integrate seamlessly with reports, profiles, and other CRM features

Creating a Company Property

Step 1: Access the Custom Fields Configuration

  1. Navigate to Customize in your CRM.

  2. Locate the Custom Fields section (company properties are managed here alongside other custom field types).

  3. Click New Property to begin creating a custom field.

Step 2: Define the Property Details

When creating a new company property, you'll need to configure:

  • Display Label — The human-readable name shown to users (e.g., "Account Tier", "Contract Renewal Date").

  • Unique Identifier — A machine-readable key used internally to reference the property. This should be descriptive and follow your naming convention (e.g., account_tier, contract_renewal_date).

  • Data Type — Choose the type of data this property will store:

    • Text — Free-form text input (e.g., company description, notes).

    • Number — Numeric values (e.g., employee count, annual revenue).

    • Select — A dropdown list with predefined options (e.g., industry, region, status).

    • Tags — Multiple values from a predefined or open list (e.g., product interests, certifications).

    • Date — Calendar date picker (e.g., contract renewal date, onboarding date).

    • Other supported types as configured in your system.

Step 3: Configure Validation and Options

  • Required vs. Optional — Specify whether this property must be filled in for every company. Required properties will display a badge during field editing.

  • Options (for Select and Tags) — If you chose Select or Tags, define the available options. For tags, you can enable typeahead suggestions to help users select from common values.

  • Validation Rules — Set any additional constraints (e.g., minimum/maximum length for text, minimum/maximum values for numbers).

Step 4: Save the Property

Click Save to create the property. It will now be available across your CRM for editing and viewing.

Editing Company Properties

Inline Editing in List Views

Once a property is created, you can edit it directly in company list views:

  1. Open your Companies list.

  2. Locate the column for your custom property.

  3. Click on the cell to edit the value inline.

  4. The appropriate editor will appear based on the property's data type (text input, dropdown, tag picker, date picker, etc.).

  5. Changes are saved automatically.

Editing in Detail Drawers

You can also edit company properties in the company detail view:

  1. Click on a company to open its detail drawer or profile page.

  2. Scroll to the custom properties section.

  3. Click the edit icon or field to modify the property value.

  4. Save your changes.

Column Management

In list views, you can control which custom properties are visible:

  • Reorder columns — Drag and drop column headers to arrange them in your preferred order.

  • Show/Hide columns — Click the Settings icon (gear) in the column header area to open the configuration panel and toggle visibility for each property.

Best Practices

1. Plan Your Properties Before Creating Them

Define what additional information you need to capture before setting up properties. Consider:

  • What business decisions depend on this data?

  • Who on your team will use it?

  • How often will it change?

  • What are the valid values or ranges?

This planning prevents creating unused properties and ensures consistency across your team.

2. Use Clear, Descriptive Labels and Identifiers

  • Labels should be user-friendly and immediately understandable (e.g., "Account Tier" rather than "AT").

  • Identifiers should follow a consistent naming convention (e.g., snake_case: account_tier, contract_renewal_date) to make them easy to reference in integrations and reports.

3. Choose the Right Data Type

  • Use Select for properties with a fixed set of options (e.g., industry, region, status). This ensures data consistency and makes filtering easier.

  • Use Tags when companies can have multiple values from a list (e.g., product interests, certifications, languages spoken).

  • Use Text only when values are truly freeform and unpredictable.

  • Use Number for quantitative data (e.g., employee count, annual revenue).

  • Use Date for time-based information (e.g., contract renewal, onboarding date).

4. Mark Properties as Required Strategically

Only mark properties as required if they're essential for your workflow. Too many required fields can slow down data entry and frustrate users. Consider making properties optional initially and marking them required only if your team consistently needs them filled.

5. Maintain Consistent Option Lists

If you use Select or Tags properties:

  • Keep option lists concise and avoid duplication (e.g., don't have both "Enterprise" and "enterprise").

  • Document what each option means if it's not self-evident.

  • Review and clean up options periodically to remove unused values.

6. Use Typeahead Suggestions for Tags

For tag-based properties, enable typeahead suggestions to help users select from common values without having to remember exact spellings. This improves data quality and speeds up data entry.

Examples

Example 1: Account Tier (Select Property)

Use case: Categorize companies by their service level or contract type.

  • Display Label: Account Tier

  • Unique Identifier: account_tier

  • Data Type: Select

  • Required: Yes

  • Options: Starter, Professional, Enterprise, Custom

  • Use: Filter companies by tier in reports, customize communication based on tier, track upgrade opportunities.

Example 2: Contract Renewal Date (Date Property)

Use case: Track when customer contracts expire so you can plan renewal outreach.

  • Display Label: Contract Renewal Date

  • Unique Identifier: contract_renewal_date

  • Data Type: Date

  • Required: No

  • Use: Set reminders for renewal outreach, create reports on upcoming renewals, identify at-risk accounts.

Example 3: Product Interests (Tags Property)

Use case: Record which of your products a company is interested in or currently using.

  • Display Label: Product Interests

  • Unique Identifier: product_interests

  • Data Type: Tags

  • Required: No

  • Options: Analytics, Automation, Integration, Reporting, Security, Support

  • Typeahead Suggestions: Enabled

  • Use: Segment companies for targeted marketing, identify cross-sell opportunities, personalize sales conversations.

Example 4: Employee Count (Number Property)

Use case: Track company size for segmentation and qualification.

  • Display Label: Employee Count

  • Unique Identifier: employee_count

  • Data Type: Number

  • Required: No

  • Validation: Minimum 1

  • Use: Qualify leads based on company size, create size-based segments, analyze deal size by company size.

Example 5: Industry Notes (Text Property)

Use case: Store freeform notes about a company's industry or vertical.

  • Display Label: Industry Notes

  • Unique Identifier: industry_notes

  • Data Type: Text

  • Required: No

  • Use: Provide context for sales conversations, document industry-specific challenges, track market trends.

FAQ

Q: Can I edit a property after creating it?

A: Yes. You can change the display label, validation rules, and option lists for Select and Tags properties. However, changing the data type of an existing property may affect how existing data is stored or displayed, so proceed with caution. If you need to change the data type significantly, consider creating a new property and migrating data manually.

Q: What happens if I delete a company property?

A: Deleting a property removes it from the configuration and hides it from all views. Depending on your system's data retention policy, the underlying data may be soft-deleted (preserved but hidden) or permanently removed. Check with your admin if you're unsure about deletion behavior.

Q: Can I use company properties in custom integrations?

A: Yes. When building custom integrations (via Custom Integration Builder), you can map query parameters to company properties using bindings. This allows external data to be looked up and displayed based on custom property values. For example, you could bind a company's account_tier property to a query parameter to fetch tier-specific data from an external system.

Q: Can I make a property required after companies have been created?

A: Yes, but be aware that existing companies without a value for that property will show an unmapped or missing notice until the property is filled in. You may want to bulk-edit companies to populate the property before marking it required, or give your team time to fill in values for existing companies.

Q: How do I reorder company properties in list views?

A: Click and drag the column headers to reorder them. Your preferred order is saved and will persist the next time you view the list.

Q: Can I hide a company property from certain users?

A: Company properties are visible to all users on your tenant by default. If you need role-based visibility, this would require custom configuration or integration with your access control system. Contact your admin or support team for options.

Q: Are company properties the same as custom integrations?

A: No. Company properties are custom fields that store data directly in your CRM. Custom integrations, by contrast, connect to external REST APIs or MCP servers and display data from those systems on company reports and profiles. You can use company properties as bindings in custom integrations to map external data lookups to specific companies.

Q: Can I import company property values in bulk?

A: Bulk import functionality depends on your system's configuration. Check with your admin about CSV import, API bulk operations, or other data import tools available in your CRM.

Q: What data types are available for company properties?

A: The most common data types are text, number, select, tags, and date. Your system may support additional types depending on your configuration. When creating a property, you'll see all available options in the data type dropdown.

Was this page helpful?