Skip to main content

Understand Core Data settings

Last updated July 23, 2026

Core Data settings define the shared choices staff use during booking, scheduling, field work, billing, and reporting. Configure them in a deliberate order so each record can connect to the records it depends on.

Before you begin​

Complete Company Profile. Decide who owns company-wide setup and how names, status, and deactivation will be managed.

Open and find Core Data​

Go to Settings → Core Data.

  1. Use Search settings... to find the visible panel name.
  2. Open a panel in the left rail.
  3. Review the list, filters, and active status.
  4. Open a record before adding a similar one.
  5. Use the panel's tabs or actions to review its relationships.

Search by the exact panel name, such as Business Units, Job Types, or Custom Fields.

  1. Create Business Units for trades, teams, regions, or brands.
  2. Create Job Types and attach their business units.
  3. Create Custom Fields for questions that staff must answer on the related record.
  4. Create Arrival Windows, zones, shifts, and scheduling rules.
  5. Organize the Pricebook.
  6. Create Campaigns for attribution.
  7. Create forms, tags, equipment choices, and other shared records.
  8. Configure Notifications.
  9. Test the complete setup in New Job.

Create or update a Core Data record​

Although each panel has different fields, the safe pattern is consistent:

  1. Search for an existing record.
  2. Click New, Add, or the panel's create action.
  3. Enter the customer-facing name.
  4. Complete required fields.
  5. Choose status and business-unit relationships.
  6. Review any job type, Pricebook, staff, zone, form, or notification relationships.
  7. Save.
  8. Reopen the record and verify the relationships.

Review downstream relationships before changing a shared record.

Understand key relationships​

  • Business Units control where Job Types, staff, Phone Service routing, forms, branding, accounting defaults, and dispatch work are available.
  • Job Types connect booking choices to business units, custom fields, Pricebook items, inventory needs, forms, notifications, dispatch, and reporting.
  • Custom Fields collect additional customer, job, location, equipment, or other record information.
  • Arrival Windows, zones, and shifts influence booking and dispatch availability.
  • Campaigns connect customer requests to marketing attribution.
  • Forms and Notifications are used when the matching job or appointment event occurs.
  • Tags provide reusable grouping across supported records.

Deactivate instead of deleting​

  1. Open the record.
  2. Review where it is used.
  3. Choose an inactive or archived status when available.
  4. Save.
  5. Confirm it no longer appears for new work.
  6. Verify historical records still show a useful name.

What happens next​

Active Core Data records become available in the daily workflows connected to them. Test booking, dispatch, customer communication, and reporting after changing a foundational record.

Troubleshooting​

A new record does not appear in booking​

Confirm it is active, attached to the selected business unit, and allowed by the related Job Type. Refresh New Job and reselect the business unit.

A Core Data panel is missing​

Clear the settings search and expand Core Data. Ask an administrator to review roles and permissions if it is still unavailable.

Historical records show an unclear value​

Restore or rename the shared record when appropriate. Prefer deactivation over deletion when old work should retain a readable relationship.