Build a network of operating locations with their own identity, service geography, time zone and authorized teams. Decide what a parent shares, what a branch controls and how changes reach the people delivering the work.
Order Now →Location identity, service decisions and administrative context stay connected.
Create an independent location or adopt configuration from an authorized parent. The location becomes both a public-facing business unit and a controlled context for the people managing its work.
Set the name, description, address, region and country. Record the business contact name, phone and email, and choose the operating time zone used for local appointments and business dates.
The office can search and filter locations, open their details and review the current operating context.
Configure a platform subdomain or custom domain as the primary host. Set whether it applies to the location or its descendants, activate the domain and use the supported DNS check and SSL setup request.
Domain behavior follows the server configuration and authorized location policy.
Manage Active, Coming Soon, Closed and Maintenance states. Record an opening date for a coming-soon location and use permitted activation, deactivation, duplication or deletion actions as the organization changes.
Core identity information can be maintained without losing the location's role in the wider operation.
The location-creation workflow combines business identity with detailed geographic setup. Set a center point, search available geography and choose the administrative or service boundaries that define the location's working area.
A common brand does not require common local prices. A shared service catalog does not require every staffing decision to come from the parent. Govern the relevant domains separately.
Branding and email templates can follow the standards the organization chooses to share. Keep the public and customer experience consistent while retaining the permitted local identity.
Services, categories, Easy Quote, pricing, invoice settings, contracts, packages and discounts can have their own inheritance policy.
Operations, geofences, routes, staff, users, customer and financial context are governed according to the enabled location relationships.
Credentials form a separately controlled domain. Available sharing follows the authorized server policy and the dependencies between the domains involved.
Continue receiving governed parent changes for the chosen domain. Use this where the parent needs to maintain an ongoing operating standard.
Begin from the parent's configuration and then manage it locally. Give a location a useful starting point while preserving subsequent local ownership.
Keep the selected domain outside inheritance. Let the local operation maintain the configuration it is responsible for.
Request a parent-child operating relationship and review it through the supported approval process. Relationships can be pending, active, suspended, rejected or revoked, giving the organization a record of the operating arrangement.
Authorized users can approve or reject a request, suspend or revoke a relationship and configure policy by business domain. Local, locked or fork-on-edit behavior is available where the enabled policy supports it.
Review the evidence, dependencies and warnings before applying a change. Supported three-way comparisons help explain differences where the underlying information supports a meaningful comparison.
A child can accept or deny a parent proposal under the applicable policy. Supported controls can lock child editing, copy settings during creation or propagate approved changes.
Publish parent change sets and review rollout, delivery and audit history. Retain the context needed to understand what was proposed and what reached the location.
Authorized administrators can move into a permitted location context through a controlled handoff. The current context stays visible, and cross-location navigation requires the applicable authorization.
That separation matters when one office oversees multiple teams, while local administrators manage the services and customer work assigned to their own operation.
Local geography and time zones inform the work at the property. The applicable configuration determines available services, pricing and the operating rules used by the location.
Customers, field teams and administrators work within the relevant business context, while parent policies govern the settings the organization chooses to maintain together.
Explore customer context →Explore brand configuration →Use location controls for branches, franchise relationships or multiple operating areas. The same feature supports shared standards and local ownership across your configured services and industries.
Advanced inheritance, domains and cross-location access follow the enabled server policy and permissions. Geographic creation tools establish the footprint during location setup.