Linked Locations

Linked Locations in Offstreet

Linked Locations allow you to group multiple parking locations together under a single parent location, so permits can be valid across several areas.

This is commonly used to create a zone-like experience (for example, “Visitor Parking,” “Event Parking,” or “Residential Zone A”) while keeping each underlying location configured and enforced normally.

Linked Locations use a parent–child structure:

• Child locations are the individual locations you have already configured in Offstreet.
• Parent locations (Linked Locations) act as a grouping layer, sometimes referred to as a Zone or Group.

At the end of this article, you’ll find a step-by-step guide that walks through how to create a Linked Location in the Offstreet dashboard.

Key concepts

Parent location (Linked Location)

A parent location is the grouping layer that users register under. It does not replace your existing locations, it simply groups them together.

Common use cases:

• A “Guest Parking” zone covering multiple garages and surface areas
• An “Event Parking” grouping across several zones
• A single registration experience across multiple structures

The parent location simplifies the registration experience without changing how your underlying locations function.

Child locations

Child locations are the individual locations you have already set up in Offstreet.

Depending on your structure, these may represent:

• Lots
• Garages
• Zones
• Permit areas
• Structures
• Event areas

This is where:

• Integrations are configured
• Enforcement occurs
• Location-level settings are managed

Linked Locations do not change how child locations operate, they simply group them.

How enforcement works

When a guest registers under a parent (linked) location, their permit is valid in all linked child locations.

• Guests only complete one registration.
• The permit is recognized as valid in every linked location.

Enforcement systems and integrations continue to reference the individual child locations exactly as they are set up. The parent location simply extends validity across them, it does not replace or override how enforcement is configured. In other words:

• The parent location controls registration grouping.
• The child locations control enforcement and integrations.

This ensures operational continuity while simplifying the user experience.

Integrations and zone names

Linked Locations do not require integrations.

• Parent (linked) locations do not have integration IDs or zone names.
• Integrations remain configured at the child location level.
• As long as each child location has integrations configured correctly, the parent location will automatically allow validity across those locations.

If integrations have not been set up yet, configure them on the child locations first, then create the linked grouping.

Registration and reporting behavior

Linked Locations create a parent–child relationship, but they do not merge data or reporting between locations.

If a guest registers at a parent (linked) location

• Reporting will show the parent location as the location of registration.
• It will not break out across all child locations.

Example:

• Guest registers using “Graduation Parking Zone” (parent location)
• Reporting shows: Location = “Graduation Parking Zone”
• Even though the permit is valid in:
  • North Garage
  • South Surface Lot
  • Overflow Area

If a guest registers at a child location

• Reporting will show only that specific child location.
• It will not roll up to the parent linked location.

Example:

• Guest registers directly at “North Garage”
• Reporting shows: Location = “North Garage”
• This registration does not appear under “Graduation Parking Zone”

Nested Linked Locations

Linked Locations can include:

• Individual locations you have configured, and
• Other Linked Locations

This allows you to build layered parking structures without duplicating configuration.

For example:

• “Event Parking Master Zone” (parent)
  • West Garage
  • East Garage
  • An existing linked location called “Overflow Parking”

This structure works well for:

• Large campuses
• Multi-property operators
• Event-based groupings

Best practice: avoid duplicate locations

When nesting Linked Locations, avoid including the same location multiple times across parent and child groupings.

Even though enforcement will still function correctly, duplicate locations can:

• Create confusion in enforcement systems
• Make the structure harder to maintain
• Complicate long-term management

A clean linked structure ensures each location is represented only once within the overall hierarchy.

Step-by-step: Create a Linked Location

Follow the guide below to create and configure a Linked Location in your Offstreet dashboard:

Need help choosing the best setup?

If you’re unsure whether to create a Linked Location, nest linked locations, or keep locations separate, reach out to your Offstreet account manager or Support. We can help recommend the best structure for your specific operational setup!