Path feature guide

Give the operation one dependable data model.

Structure business records and relationships so Apps, workflows, and AI can use the same context.

Product screenExample data

What this makes possible

Start with the work, then shape the system.

01

Operational records

Model customers, products, properties, projects, people, and the relationships between them.

02

App data

Give each App a durable data foundation with the access boundaries it needs.

03

Connected context

Bring selected external records into workflows without losing source identity.

How to approach it

A practical starting path.

The exact implementation depends on your data, permissions, operating model, and connected systems.

  1. 01

    Name the records

    Start with the business nouns, their identifiers, and the relationships the workflow depends on.

  2. 02

    Define ownership

    Choose the source of truth, required fields, access rules, and update responsibility.

  3. 03

    Design for change

    Plan imports, validation, history, and how the model evolves as the business does.

Keep exploring

Related systems and capabilities.

Build your version.

Start with one useful workflow, then connect the rest as the system proves itself.