Skip to main content

​
What is an object?

An object is a category of data in Qwoty — a type of thing your team works with. Each object has a fixed schema of system fields plus, for some of them, custom fields you add to match your business. When you open Settings → Data → Data model, you see the full list of objects. Each one carries a badge that tells you whether you can extend it.

​
Standard vs Manageable

Qwoty splits objects into two categories:

​
Manageable objects (4)

These are the objects where you can add custom fields:

​
Standard objects

The remaining objects use a fixed schema. You can browse their fields and integrate with them, but you can’t add custom fields directly: Address, Approval, Billing Frequency, Bundle, Business Unit, Catalog, Contact, Content Block, Customer Segment, Discount, Integration, Order, Payment Method, Payment Term, Pricebook, Sales Agreement, Tax, Template, Workflow.
Even though Quote is shown as a manageable object via its Template, the Order that follows a signed quote is Standard. Order data flows from the Quote at signature time — you don’t customize the Order schema directly.

​
How to know if an object accepts custom fields

Open Settings → Data → Data model and look at the badge next to each object’s name:
  • Standard badge → no custom fields can be added
  • Manageable badge → you can add custom fields via + New at the top of the field list
Inside a manageable object, system fields show a System badge in the Type column (read-only). Fields you add show a Custom badge with Writable API access.

​
Why some objects are Standard

Standard objects power core Qwoty behavior — pricing, taxation, approvals, ordering. Their schemas are locked because:
  • Consistency — every workspace handles them the same way, so integrations and exports stay predictable
  • Stability — adding a field on a core object would risk breaking quoting math, contract generation, or order generation
  • Performance — system objects are heavily indexed for fast queries; custom fields on them would degrade lookup speed
When you need data on a Standard object, the convention is to put it on the related Manageable object instead. For example: a Bundle is Standard, but the Product included in that Bundle is Manageable — add the custom field on Product, not Bundle.

Field types

The three data types you can pick when adding a custom field.

Field properties

Mandatory, Editable, Display — control how a field behaves on each object.

Data model overview

Concepts behind the Qwoty data model.

Manage roles

Control who can edit the data model.