Sign in Start free trial
Platform

Configuration Studio

Shape  AI to your business without code: fields, forms, rules, lists and visibility.

The configuration studio lets business admins and implementers add and rename fields, design forms, set rules, manage lists and choose who sees what. Changes are versioned, audited and can be promoted from test to production. Hiding is always preferred to deleting, so data is kept and nothing built is lost.

55 features available 6 planned 9 capability areas
Highlights

What stands out

Your words on every screen

Rename fields once and reports, notifications and the assistant follow.

Design a form like a page

Sections, columns and show-when rules with a preview as any role.

Hide, never lose

Hidden fields keep their data and can come back.

Promote with confidence

Change sets are checked, approved by a second person and reversible.

Configure by asking

Use  AI or your own AI tool to propose configuration for a person to confirm.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Fields

Add the fields your business needs and rename the ones it already has.

11 features
  • Custom fieldsText, long text, number, currency, percent, date, picklist, multi-picklist, yes or no, lookup, e-mail, phone and web address, with exact decimals.
  • Field studioA friendly builder: give a label and options, and  AI creates the key and picklist.
  • Tenant wordsRename any field or object to your company's naming; the assistant, reports and documents use your words.
  • Rename standard fieldsRelabel built-in fields without breaking integrations.
  • Required, read-only and conditional rulesMake a field required or read-only when a condition is true.
  • Default values, help text and per-language labelsGuide people as they fill a form.
  • Field constraintsRequired, minimum and maximum, length and pattern checks.
  • Expression fieldsComputed values from a governed formula language.
  • Sensitive and encrypted fieldsHide sensitive fields from administrators until granted and encrypt chosen fields with tenant keys.
  • Field limits and stable keysKeys never change; custom field keys cannot collide with the product's own.
  • Auto-numberingPlannedAutomatic sequence numbers per type.

Objects and record types

Extend the data model without a developer.

5 features
  • Custom objectsCreate your own record types with fields and relationships that automatically get an API, assistant actions, reports and approvals.
  • Object catalogueSee every standard and custom object with its fields.
  • Record typesDifferent forms, lists and processes for different kinds of the same record.
  • Lookup relationshipsLink records to each other.
  • Schema diagramPlannedA visual map of object relationships.

Forms and layouts

Design the screens people use.

8 features
  • Form designerPer object, any number of layouts for a record page, a create form or a process action, with tabs, sections and one to three columns.
  • Show-when conditionsShow a field or section only when a rule is true.
  • Layouts per role, record type and statusDifferent layouts for different people and stages.
  • Preview as a roleSee exactly what a role will see before publishing.
  • Layout versionsDraft, publish and archive layouts.
  • Smart defaultsMaximum fields are pre-filled from context and history; sensitive fields are never remembered.
  • Custom app pagesCompose your own pages from governed building blocks.
  • Public intake formsPlannedForms for outsiders that write into any object through the same validation.

Lists and views

Every list is searchable, sortable and saveable.

7 features
  • One list engineSort, filter, search, totals and paging under the viewer's own access on every list.
  • Saved viewsPersonal and company views, with a company default and a personal default.
  • Nested filtersGroups of and or conditions up to a safe depth.
  • As-of datesRead dated lists as they were on a date.
  • Bulk editChange many rows at once with validation.
  • Download a template and uploadSpreadsheet import and export on nearly every list, generated from the same rules as the API.
  • Kanban, calendar and map viewsPlannedBoard and calendar presentations of lists.

Rules and data quality

Keep data clean without code.

5 features
  • Validation rulesConditions that block a save with a clear message, tested before activation.
  • Uniqueness and duplicate rulesEnforce unique values or warn about look-alikes, with a preview of existing clashes.
  • Picklists with retirementAdd values and retire them without losing data.
  • Behaviour rulesConditional required, read-only and visibility by record state.
  • Global picklists shared across objectsPlannedOne value set used in many places.

Hide, never delete

Fewer fields on screen without losing anything.

6 features
  • Hide and unhide fieldsHidden fields leave every surface but their data is kept.
  • Soft delete with restoreDeleted custom fields can be restored within a retention window you set.
  • Personal view changesAny member can hide a field in their own view, with undo.
  • Company view changes with previewAdmins change views for everyone after a preview.
  • Required fields stay visibleA field the system needs is never hidden from a record screen.
  • Hidden fields kept out of AIHidden and inactive fields are not sent to a model.

Visibility and access

Choose who sees which fields and menus.

6 features
  • Navigation visibilityShow or hide menu items per role.
  • Navigation treeA collapsible hub, sub-module, category and function tree with favourites and recents.
  • Field permissions by roleRead, write or hidden per field and role; hidden means absent.
  • Per-user UI preferencesEach person's own settings, such as themes and layout choices.
  • Four design themesOpti, Core, Glass, Command and Classic themes.
  • Turn hubs and modules on or offWithin your licence, menus, home and assistant adapt.

Tenant settings and templates

Company-wide settings and ready-made starting points.

5 features
  • Industry starter packsVersioned packs for several industries with sample data, applied to licensed hubs only.
  • Template galleryPreview and apply templates in the tenant's own currency.
  • Setup checklistGuided setup of what is left to configure.
  • Policy choices as settingsChoices are tenant settings with safe defaults rather than fixed in code.
  • Document and e-mail templates with brandingPlannedBranded templates per entity.

Lifecycle: audit, version, promote

Change safely and prove what changed.

8 features
  • Config auditEvery configuration write records who, what and before and after.
  • Config versionA monotonic version per tenant drives cache refresh and drift detection.
  • Change setsPackage configuration, validate, approve by a second person, deploy and roll back.
  • Environment linksLink test and production tenants of one subscription for promotion.
  • Drift detectionSee and accept direct changes made outside a change set.
  • Configuration as codeExport and apply versioned files validated by a published schema, from the command line or an AI tool.
  • Many configuration kindsFields, rules, layouts, processes, plans and hub setups travel as typed kinds.
  • Versioned business recordsEffective-dated versions of plans, products and similar records.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Add or hide a field on a screen for a person or the company
  • Preview a uniqueness rule against existing data
  • Propose a layout change for confirmation
  • Prepare a configuration change set
  • Describe an object and its fields
  • Suggest default values for a form
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to Configuration Studio.

Workflow

Change sets, layout publication and shared artefacts can require approval from a different person, and custom fields can be used as facts in approval rules.

  • Production change set needs a second approver
  • Custom field used in an approval condition
  • Layout publish approved before going live

Reporting and analytics

Custom fields become reportable automatically with field security kept.

Datasets

Custom fields in every hub's datasets

Integration

Custom fields and custom objects appear in the API, the OpenAPI document and AI tool actions.

/v1 custom objects and field definitions

Events

Config deployed

Migration

Spreadsheet import with validation is available on nearly every list.

Mobile

On the phone

Layouts follow the phone frame; dashboards have their own phone layout.

Who uses it

Business administratorImplementerIT configuratorAny user (personal view)Reviewer approving a change set

Industries

  • Industry starter packs exist for several industries with sample data
Questions

Frequently asked

Can we rename fields to our own terms?

Yes. Renames apply across screens, reports, notifications and the assistant for your company only.

Can we add our own record types?

Yes, custom objects get an API, reports and approvals automatically.

What happens when we hide a field?

It disappears from every screen but its data is kept, and it can be restored.

Can we test before production?

Yes. Package changes as a change set, validate, approve and deploy, with rollback.

Can people change their own view?

Yes, personal changes with undo; company changes need a preview and a confirmation.

Can we configure from code?

Yes, configuration can be exported and applied as versioned files through the command line.

Are there limits?

Yes, per-object limits on custom fields apply.

See Configuration Studio on  AI

Talk to us