​

Object Manager

The Object Manager is your central hub for configuring Statisfy’s data model. Manage fields across all entity types, set up products and dimensions, configure CRM sync, and create custom objects.

​

Accessing Object Manager

Navigate to Settings > Object Manager (app.statisfy.com/settings?tab=object-manager). You need admin permissions to access this page.

​

Entity Tabs

The Object Manager is organized by entity type. Select a tab at the top to manage that entity:

​

Field Categories

Within each entity tab (except Product and Custom Objects), fields are organized into collapsible sections. Each section shows a badge with the field count.

​

Supported Field Types

​

Creating a Custom Field

1. Select the entity tab (e.g., Accounts)
2. Click + Create Field in the top-right corner
3. Enter a Field Name and choose a Field Type
4. Optionally check This is a formula field to make it a computed field (see Formula Fields)
5. Click Save

The new field appears under the Statisfy Fields section. Additional settings — display name, editability, CRM mapping, picklist/pill options, and so on — are configured afterward by editing the field.

​

Editing a Field

Hover over any field and click the pencil (edit) icon next to its name to open the Edit Field dialog. The available options depend on the field type and whether it’s a standard, Statisfy, or CRM field.

​

Options for Statisfy (Custom) Fields

​

Options for CRM Fields

​

Options for Opportunity and Projects/Tasks Fields

These entity types have additional field-level controls:

​

Filter Conditions on mandatory opportunity fields

When you turn on Mandatory for an opportunity field, you can attach Filter Conditions so the field is only required when the opportunity matches. The builder is the same one used elsewhere in Object Manager, and every condition shape it exposes is enforced when the opportunity is saved:

• Stage, owner, and other picklists — is, is not, in, not in.
• Numbers, dates, and datetimes — equals, greater than, greater than or equal, less than, less than or equal. Date fields also support the builder’s relative-date presets (in the last…, not in the last…, between…, including fiscal-quarter presets, which use the same fiscal-quarter start as segment filters).
• Multi-select and lookup fields — contains, in, and not in match against the selected members, not the container.
• Derived opportunity conditions — is closed and is won are evaluated against the pending stage change, so a rule like “Close reason is required when the deal is closed” fires on the save that closes the deal.
• Grouped logic — mix AND and OR groups; empty groups are ignored rather than treated as matched.

Hidden fields are never enforced, even if their conditions match. A value of 0 or false counts as a real value, so a number field the user genuinely set to 0 passes the check and a field the user left blank does not.

​

Picklist and Pill Options

For picklist (dropdown) fields and pill (colored label) fields, the edit dialog includes an options editor where you can add, remove, and reorder the available choices. Pill options also support setting a custom color for each value.

​

Lifecycle Stage Fields

Stage-type fields — such as an opportunity’s Stage — appear in Object Manager with the Lifecycle Stage type. Their edit dialog includes a stages editor where each stage has:

• a display label — the friendly name users see everywhere the stage appears, including list views, filters, and CSV exports
• an identifier — the stored value behind it; identifiers must be unique within the field

You can add, rename, and remove stages from the same editor. Renaming a stage’s display label doesn’t change the stored value, so existing records, filters, and CRM sync are unaffected.

​

Formula Fields

Formula fields are special custom fields whose values are computed automatically from an expression you define. They are read-only — users cannot edit their values directly.

​

Creating a Formula Field

1. Select an entity tab and click + Create Field
2. Choose a field type (Text, Number, Date, Boolean, Currency, etc.)
3. Check This is a formula field and click Save
4. The formula editor opens — select a formula type and configure it
5. Use Validate to check for errors, Preview to test against sample records, then Save

​

Available Relationships for Rollups

Rollup and cross-object formulas traverse relationships to access related data. The available relationships depend on the entity type:

​

Editing a Formula Field

Formula fields show an Edit Formula link in the field edit dialog. Click it to open the dedicated formula editor where you can modify the expression, change the formula type, or update filters and aggregations.

​

Deleting a Custom Field

1. Click the trash (delete) icon on the Statisfy field you want to remove
2. Confirm the deletion in the dialog

​

CRM Sync Configuration

​

Upstream Sync Toggle

For CRM field sections (Salesforce, HubSpot), an Enable upstream sync checkbox appears in the section header. It controls whether edits you make in Statisfy are sent to your CRM for that entity type. It does not change what Statisfy pulls from your CRM. For Opportunity, it also makes CRM opportunities editable in Statisfy. Accounts use the checkbox in their own Account CRM Fields section. Meetings do not use a checkbox: set the Upstream Target Object of Meeting Activity (see below). For HubSpot, see Sync changes back to HubSpot. When you turn on the checkbox for People or Opportunity, Statisfy first shows a confirm dialog with what the first sync will do in your CRM:

• People: how many contacts Statisfy will update, how many it will create or link, how many it will skip, and how many it cannot create.
• Opportunity: how many opportunities (deals in HubSpot) Statisfy will update and create, and how many it will skip because their account is not linked to the CRM.

Select Turn on to save the setting, or Cancel to leave it off. If the counts cannot be read, the dialog says so, and you can still turn the sync on. Turning the checkbox off needs no confirm.

​

When Statisfy does not create a contact

Statisfy does not create a new contact in your CRM when:

• The person has no customer.
• The person’s customer has no CRM account. Statisfy creates the contact once the account is linked.
• The person’s email uses your company’s own domain or an alias domain. These are your own staff.
• The person has no name, title or role. HubSpot also needs an email.

These people are counted as skipped or not created in the confirm dialog. Their changes stay pending, so the next sync creates the contact once the cause is fixed. Contacts that are already linked to the CRM still update.

​

Push to CRM

The Push to CRM setting in the Edit Field dialog of a Statisfy field picks which CRM field receives the field’s value when upstream sync runs. Each row names one connected CRM and one field in it.

1. Open the field’s Edit Field dialog.
2. Under Push to CRM, type in the field box to search the CRM’s fields, then select one.
3. To push an account field to another CRM, click + (Add a CRM) and pick the CRM. A new row appears for it.
4. To stop pushing to a CRM, click X on its row. With no rows, the field shows Not pushed to a CRM.
5. Click Save.

Rules for push targets:

• Only account fields can push to more than one CRM. Other fields push to one CRM.
• Each CRM gets one target field.
• Salesforce and HubSpot cannot be targets of the same field. Statisfy links an account to one CRM account ID. You can pair either one with Gainsight.
• The CRM field’s type must be able to hold the Statisfy field’s type. For example, a number field pushes to a number or text field, and a date field pushes to a date field. Statisfy lists only the CRM fields that fit.
• A row with no field selected blocks save. Select a field or remove the row.

When upstream sync runs, Statisfy pushes each changed account value to every CRM it targets in the same run.

​

Field Mapping

You can map fields between Statisfy and your CRM in two directions:

• Upstream CRM Field — On Statisfy custom fields, select which CRM field should populate this field (CRM → Statisfy)
• Push to CRM — On Statisfy custom fields, select which CRM fields receive this field’s value (Statisfy → CRM). See Push to CRM
• Downstream Statisfy Field — On CRM fields, select which Statisfy custom field this CRM field should populate (CRM → Statisfy)

​

Per-Field Upstream Target Object

Some standard fields contain rich, nested data (most notably Activity fields like Meeting Activity and its Transcript sub-field) that doesn’t map cleanly to a single CRM column. For these fields, Object Manager exposes an Upstream Target Object picker so you can choose exactly which CRM object the data should land in.

1. Expand the field in Object Manager. Fields that support per-field sync show an Upstream Target Object button under the field header.
2. Click the button to open the target-object picker.
3. Pick the destination object in your connected CRM — for example, sync Meeting Activity into Salesforce Event or Task or HubSpot Call, and sync the Transcript sub-field into a custom long-text field on the same object.
4. Save. From the next sync onward, Statisfy writes the field’s value to the selected target object whenever the record changes.

Conditions that must be met for the picker to be active:

• A CRM integration (Salesforce or HubSpot) is connected
• For sub-fields like Transcript, the parent field (Meeting Activity) must have upstream sync enabled first — otherwise the picker shows “Enable Meeting Activity upstream sync to configure transcript sync.”

​

Meeting Activity Push to Salesforce

When Salesforce is your connected CRM, the Meeting Activity field’s Upstream Target Object does more than store a preference — it turns on the meeting push. Set it to Event or Task and Statisfy creates a Salesforce record for each meeting activity from the next sync onward. This is fully self-serve; you don’t need Statisfy support to enable it. 1. Choose the destination. On the Activity tab, expand Meeting Activity and set the Upstream Target Object to Event or Task. Saving a destination enables the push. 2. Map meeting fields (optional). Meeting Activity exposes AI-computed sub-fields you can map to fields on the destination object: Map each sub-field to the Salesforce field where it should land. For example, map Full Recap to the Event or Task Description field to push the recap as the record’s description. Mappings are optional — with no mappings, Statisfy still creates the basic Event or Task. 3. Push meeting participants (optional). Once a target object is saved, a Salesforce-only Push meeting participants toggle appears under the field. It’s off by default. When on:

• Event destination — every meeting attendee is attached to the Event as a related attendee. External participants are matched to Salesforce Contacts (by the synced CRM contact, or by email lookup) and internal reps to Salesforce Users. Participants with no matching Contact or User are skipped. Repeat syncs don’t create duplicate attendees.
• Task destination — a Task has no attendee list, so the primary external contact is set as the Task’s related contact (WhoId) instead.

​

Projects/Tasks and Activity: Sub-Type Configuration

For Projects/Tasks and Activity entities, fields can be configured per sub-type (e.g., per task type or per activity type). This allows you to:

• Show or hide a field for specific task/activity types
• Make a field mandatory only for certain types
• Associate custom fields with specific sub-types

​

Products & Dimensions

The Product tab has a dedicated interface for managing your product catalog and usage dimensions. Each product appears as a card with its details, its dimensions, and controls for editing, adding dimensions, and reordering.

​

Creating a Product

1. Go to the Product tab
2. Click + Create Product
3. Fill in the product details:

4. Click Create

​

Editing a Product

Click the pencil icon on a product card to open the edit dialog and update its settings.

​

Deleting a Product

To delete a product from the catalog:

1. Navigate to the Product tab in Object Manager
2. Click the delete icon on the product card

​

Deleting Dimensions

To remove dimensions and all their associated data from a product:

1. Click Delete Dimensions on the product card
2. A warning dialog will appear — review it carefully, as this action removes both the dimensions and all associated usage data
3. Confirm to proceed

After deleting dimensions, the product’s delete button becomes enabled if you also want to remove the product itself.

​

Clearing Dimension Data

To remove usage data for a product’s dimensions while keeping the dimensions themselves:

1. Click Clear Dimension Data on the product card
2. A warning dialog will appear — review it carefully, as this action removes all stored usage data for the product’s dimensions
3. Confirm to proceed

After clearing, the dimensions remain configured on the product but contain no associated data. New data can be imported again via CSV or integrations.

​

Managing Dimensions

Dimensions are measurable attributes associated with a product (e.g., active users, storage used, API calls). Each product card shows its dimensions below the product details.

​

Adding a Dimension

1. Click + Add Dimension on the product card
2. Enter the dimension name
3. Select the dimension type:

4. Configure display settings (see below)
5. Click Create

​

Dimension Display Configuration

When creating or editing a dimension, you can configure how values are displayed:

​

Reordering Dimensions

Drag and drop dimensions using the grip handle to change their display order on the product usage widget.

​

Dimension Visibility

Toggle the eye icon on a dimension to show or hide it from the product usage widget without deleting it.

​

Custom Objects

Custom objects let you create entirely new entity types beyond the standard ones. Creating a Custom Object:

1. Navigate to the Custom Objects tab
2. Click + Create Custom Object
3. Define the object name and description
4. Add fields to capture relevant data
5. Save the custom object

Once a custom object has records, the account page’s Objects tab has a sub-tab per custom object listing that account’s records. See Account Page Navigation. Custom objects can also be used in filters and workflows.

​

Editing Record Values

Users can edit a custom object record’s field values directly — inline in the record grids and in the record detail sheet. As an admin, you control which fields are editable:

• Fields created in Statisfy are editable as soon as they exist.
• Fields synced from a CRM are locked by default. To unlock one, edit the field and turn on Editable. Edits to synced fields also require the object’s Sync to Salesforce writeback to be on, so the change can be pushed back to the CRM. See the Salesforce Bi-Directional Sync Guide.

Locked fields show a tooltip explaining why they can’t be edited and where to change that. Inline editing supports these field types: Text, Long Text, Text List, Number, Float, Percent, Percent Ratio, Currency, and Boolean. Other types (such as Date, URL, Pill, and Lifecycle Stage) remain read-only for now.