How Locations work in Continu — added to user profiles, used to search, assign, and segment. Supports two levels of sub-locations.
Locations are how Continu represents user geography. Like Departments, they land on user profiles and drive search, assignment, segmentation, and reporting. Locations support two levels of sub-locations below the parent — useful for orgs that need country → region → city granularity.
For broader user management context, see User Management: Who Has Access to What, and Why.
How to Manage Locations
Navigating to Locations. From the left-hand navigation, click Connect > Locations.
Adding a Location
Step One: Navigate to Connect > Locations.
Step Two: Click the Add A Location text cell, enter the Location name, click the + icon to finalize.
Adding a Sub-Location or Sub-Sub-Location
Step One: Navigate to Connect > Locations.
Step Two: Click the parent Location you're adding a Sub-Location to. The Sub-Location column highlights.
Step Three: Click the Add A Location text cell in the Sub-Location column, enter the name, click the + icon.
Repeat the same pattern for Sub-Sub-Locations — click the Sub-Location, then add into the third column.
Editing a Location
Click the pencil icon, change the name, click the check icon.
Deleting a Location
Click the pencil icon, then the red trash can icon. Users previously assigned to the deleted Location lose that attribute.
Considerations
Match the level of granularity your programs actually need. If most programs are scoped at the country level, country-level Locations are enough. If you frequently scope by city or office, build the hierarchy out.
Use a consistent naming convention. "United States" vs "US" vs "USA" creates confusion downstream. Pick one and apply it consistently — and match the HRIS if syncing.
Plan for new offices. When the org opens a new office, the Location list needs to update. Coordinate with HR or office operations so additions land in Continu in time.
Reserve Sub-Sub-Locations for genuine third-level distinctions. Country → Region → City is meaningful. Adding a fourth level (Country → Region → City → Floor) is rarely useful.
Configuration Pitfalls
Mixed Naming Conventions. "USA" in some user profiles and "United States" in others means Smart Segments capture only one set. Audit existing user data for naming consistency.
Deleting Locations With Active Users. Users in deleted Locations lose the attribute. Reassign before deleting.
Encoding Office Type Instead of Geography. "Remote" or "HQ" mixed with city names ("New York," "London") makes Location queries inconsistent. Use a separate attribute for remote/office status.
Three-Level Nesting When Two Is Enough. Over-nesting Locations makes profiles harder to maintain and Smart Segments harder to write. Use the minimum granularity that supports your programs.
Forgetting Location Drives Automations and Smart Segments. Renaming or restructuring Locations can break downstream Automations and Smart Segments silently. Audit before significant changes.
Where This Fits
You're here because you're setting up or managing Locations. For broader user attribute management, see User Management: Who Has Access to What, and Why.
See Also
- User Management: Who Has Access to What, and Why — the strategic anchor.
- Departments In Continu — department attribute.
- Levels in Continu — level attribute.
- Skills in Continu — skills attribute.
- Automation Audience Trigger Guide — how Locations drive Automations.
Match HRIS naming and granularity. Consistent naming convention across all Locations. Reassign users before deleting. Two levels of sub-locations is usually enough.