Path feature guide

Put the experience on an address your audience knows.

Use a branded domain for a published Customer app or website when the delivery setup supports it.

Product screenExample data
www.your-domain.com
Harborline
Inquire

Owner & operator

One site for the businesses you run

Company, property, and project pages read from the same Path records your operators work in.

View holdings
Team →
Operators reviewing a portfolio together
Harborline operations12 companies
Harborline Ops
Operating company
Westfield Place
Multifamily
Northline Works
Capital project
Advisory desk
Client work

What this makes possible

Start with the work, then shape the system.

01

Branded websites

Publish a public site at the company or product domain visitors expect.

02

Customer portals

Give customers and partners a recognizable address for their shared workspace.

03

Product experiences

Deliver a Customer app under a domain that fits the product and audience.

How to approach it

A practical starting path.

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

  1. 01

    Choose the address

    Decide whether the experience belongs at a root domain or a focused subdomain.

  2. 02

    Connect DNS

    Add the required records with the domain provider and wait for them to become available.

  3. 03

    Verify production

    Confirm routing, TLS, redirects, canonical URLs, and the complete live experience.

Keep exploring

Related systems and capabilities.

Build your version.

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