How Inheritance Works
In swivl, your Organization's structure is hierarchical:
Organization → Group → Location
Settings and information flow top-down through this structure.
-
Organization-level settings apply to all Groups and Locations.
-
Group-level settings override Organization settings, but only for the Locations within that Group.
-
Location-specific settings take precedence for that individual Location.
This setup allows you to manage global standards across your Organization while giving flexibility to Groups and Locations that need custom settings.
❗Important: A few fields in the Location “Details” section do not inherit from the Organization or Group levels. These must be set at the Location level if needed. See the 'What Needs to Be Filled Out' section below for details.
How to Create a Group
-
From the Property Manager dashboard, click the three dots menu.
-
Select Add Group.
-
Enter a Group name, then click Create.
-
Set any specific details or settings you want to apply to this Group.
-
Save your Group.

Tip: Only create a Group when you need Locations to share settings different from the Organization defaults.
How to Create a Location
-
From the Property Manager dashboard, click the three dots menu.
-
Select Add Location.

-
Enter the Location’s details (e.g., name, and select the Group you want the Location to be part of).
-
Click Create to save the Location.

Note: Locations inherit settings from the Group they are in, unless you customize them at the Location level.
What Needs to Be Filled Out?
When setting up a Location, not all fields inherit from the Organization or Group. The following fields must be filled out manually at the Location level unless otherwise noted:
🔹 Location Information
-
Location Website URL – Add the full public URL for the Location. (e.g. https://www.swivlstorage.com/cities/merlin)
-
URL Lookup Pattern – Required for proper functionality; the part of the URL that comes after '.com' (e.g. /cities/merlin)
⚠️ Tip: Make sure none of the URLs end with a backslash (/) — this can cause issues with lookups and redirects. Always enter URLs without a slash at the end. -
Postal Code – Leave blank until the Location is ready to launch.

🔹 Location Features
-
FMS Integration – Enable this to sync your Location with your FMS.
-
FMS ID – Leave blank until you're ready to send messages (if Sequences are enabled).
-
FMS Sync Enabled – Set this according to your integration status.

🔹 Important URLs
-
Location Specific Payment Portal – Add only if the Location uses a different payment page.
-
Google Review – Add the URL to the Location’s Google Review page.

🔹 Hours
-
Hours – Enter the Location’s business hours, access hours, and call center hours manually.

🔹 Advanced Settings
-
Google Review Place ID – Required if you want swivl to manage replies to reviews.
-
Outbound Twilio App – Only needed if each Location has a unique phone number.

🔹 Spot.is
-
Spot Location URL – Add the unique Spot URL for the Location.
-
Spot Location Short Link URL – Shortened version of the Spot URL for sharing.

Best Practices
-
Set global policies at the Organization level whenever possible.
-
Use Groups to manage Locations with shared needs (e.g., regional offices, departments).
-
Customize at the Location level only when necessary to reduce complexity.