Skip to content
Help Center
Submit a request Sign in

Configure custom data tables and fields

Data Tables adds structured information to company or contact records. Separate table access, field access and display choices let you collect useful data without crowding the main record form.

Applies to: Supportbench Core. Location: Settings → Configuration → Data tables. Editing requires Administer fields.

Before you begin

  • Decide whether each row belongs to a Company or a Contact, and which staff/customer roles may read or maintain it.
  • Plan the hierarchy before saving. Location and parent are immutable; empty role selections mean all applicable roles, not nobody.

Configure and verify

  1. Open Settings → Configuration → Data tables and choose New Data Table.
  2. Enter System name and Display name. Choose Company or Contact Location and, if needed, a parent table with the same Location before the first save.
  3. Review Active, Internal roles, Customer roles and Display settings. Leaving role selections empty allows all applicable roles.
  4. Choose Save Changes and reopen the table. Location and parent cannot be converted afterward.
  5. Choose Add Field, select its Type and configure field names, access, order and Active. Save the field before adding dropdown options. Field type is immutable after saving.
  6. For supported list fields, add options with the intended labels, Parent, Order and Active values. Read the lifecycle rules below before moving or deleting options.
  7. Open the intended Company or Contact, enter approved synthetic data and save it. Test both intended and excluded staff/customer roles at table and field level.

Settings reference

Details and hierarchy

SettingWhat it controlsHow to choose
System name / Display nameEach up to 50 characters; description up to 250.Use a stable system name and a readable display name.
LocationCompany or Contact; immutable after creation.Choose the consuming record type first.
Parent tableAn active parent at the same location; immutable after creation.Plan the hierarchy before saving.
ActiveInactive tables retain stored values but are hidden from new data entry.Deactivate only after checking where the table is used.
Saved Core Data Table named Demo Equipment Registry with a stable system name, synthetic-data description and Active off.
Use a stable internal System name and a clear Display name. This training table is inactive and has no customer values. Review access and field design before operational use.

Access and display

SettingWhat it controlsHow to choose
Internal roles / Customer rolesRestricts table access; an empty role selection means all applicable roles.Verify both intended and excluded audiences.
Display orderValues from 0–20.Place frequent tables first.
Hide empty columnsControls display of empty columns.Enable when sparse data would otherwise obscure populated values.
Saved Company data table with immutable Location and Parent, Support team lead internal role and Harbor training readers customer role.
Choose table-level roles explicitly. Empty role selections allow all applicable roles. Location and Parent become locked after the first save. These are example roles; verify your own allowed and excluded readers.

Fields and options

SettingWhat it controlsHow to choose
Field name / DescriptionName up to 50 and description up to 250 characters.Explain what users should enter.
Field typeImmutable after creation: supported types include Checkbox, Date/time, Dropdown, Text, Multiline, Integer, Money, Tags, Encrypted Text and Encrypted Password; historical types can remain fixed.Choose the stored data type before collecting values.
Field roles / OrderField access plus order from 0–20.Review field restrictions independently of table access.
Option label / Parent / Order / ActiveOption label up to 200 characters; active parent; order 0–25.Save the field before defining its options; keep parent/child meanings consistent.
Field ActiveInactive fields retain stored values but are hidden from new data entry.Use deactivation to retire an input without claiming its historical values were erased.

Behavior to know

  • Deleting a table preserves its field/value data; do not treat table deletion as a data-erasure operation.
  • Deleting an option does not delete its child options. Moving an option resets its children to root; review the resulting hierarchy.
Saved Service reference field with non-sensitive example guidance, locked Text box type, display order zero and Active enabled.
The Service reference field uses Text box for a value such as EQ-TEST-001. The field type is locked after creation. Its Active switch is separate from the parent table, which remains inactive in this demonstration.
The saved Service reference field Access tab with separate internal and customer role selections.
Review field access independently of table access. Saving these choices verifies configuration only; test both intended and excluded staff and customer identities before storing sensitive information.

Recommended use

  • Use terminology that agents and customers already understand. Explain the intended meaning in the description.
  • Keep the initial configuration small enough for people to choose consistently. Add options when they represent a real operational difference.
  • Review existing references before renaming, changing scope, or deleting. Where supported, deactivate an obsolete option before considering permanent deletion.

Worked example: keep a Company equipment register with deliberate access

  1. A support operation needs a Company-level equipment register containing a service reference, warranty date and service status. Confirm whether an existing Asset workflow already meets the need. A custom Data Table stores structured customer information; this example does not create automatic links to Assets or Case routing.
  2. Choose New Data Table, give it a stable System name and readable Display name, and choose Company as Location. Plan any Parent table before the first save because Location and Parent are immutable afterward.
  3. Select the actual intended Internal roles and Customer roles rather than leaving the selections empty to try to restrict access. Empty means all applicable roles. If the desired restriction cannot be expressed by the available controls, resolve that access requirement before entering sensitive data.
  4. Save Changes, then Add Field for the service reference, warranty date and service status using appropriate Text box, Date/time and Dropdown types. Save each field before adding its choices. Choose field-level roles for any sensitive field separately from table-level access; type is locked after saving.
  5. On an approved test Company, enter synthetic values such as EQ-TEST-001, an agreed test date and a clearly defined service-status choice. Save and reopen the customer record to check the data appears under the intended table and fields.
  6. Test both allowed and excluded staff/customer identities at table and sensitive-field level. A successful configuration save or an agent’s own view does not prove the customer boundary. If too much appears, inspect empty role selections and the independent field access before entering real data.
  7. Assign an owner to maintain warranty and service information. These stored values do not themselves establish a contractual entitlement, send reminders or update Case deadlines. Review existing records before retiring a field or table; deletion is not a data-erasure procedure.

Troubleshooting

ProblemWhat to check
The table is not on the customer recordCheck Company versus Contact Location, Active and role scope.
The table appears but a field is missingCheck that field’s Active and separate access settings.
Everyone can see the tableEmpty role selections permit all applicable roles. Review both Internal roles and Customer roles.
Location, parent or field type is lockedThese saved choices are immutable. Assess existing values and references before planning a replacement.
Deleting a table did not erase valuesTable deletion preserves field/value data; it is not an erasure workflow.
Moving an option changed its childrenMoving an option resets its children to root. Review and restore the intended option hierarchy.
  • Customers → Manage companies and customer organization details
  • Customers → Manage contacts and customer portal access
  • Organization → Configure agent roles and division access
  • Customers → Configure customer roles

Was this article helpful?