⚠️ This article applies ONLY to the New Version of Locations.
How do you know if you have the New Version?
→ You see the “Locations” option directly in the main DataScope menu (not under Settings > Lists).
→ When you open it, you see a list with columns such as: Location Name, Number of Users, Last Activity.
If you do not see this, you are probably using the Old Version → [link]
The Locations feature allows you to organize, classify, and manage the different physical or operational spaces within your organization, such as plants, branches, warehouses, offices, or production lines.
Important: this is the new version of Locations, which will temporarily coexist with the previous version while users migrate to this new experience.
📍 What are Locations used for?
Locations help you:
Structure your operation hierarchically (locations and sublocations).
Associate forms, tickets, and other records with a specific location.
Filter information by location from the Home section.
Control access based on user permissions.
Centralize contact and location information.
📍 Accessing the Locations section
You can access Locations from the main DataScope menu. There, you will see a list of all created locations.
In this view, you will find:
Location name
Number of users with access
Last recorded activity
Available actions
📍 Available actions for a Location
From the actions column, you can:
View the location
Edit its information
Delete the location
Create sublocations
Additionally, from the main view you can import or export locations, making bulk uploads or external data management easier.
📍 Create a new Location
To create a location, click Create location and complete the required information.
👉Basic information
Name: location name.
Location code (optional): unique identifier. If left blank, the platform will generate one automatically.
Location type: defines the type of facility. Some available options include:
Company
Plant
Warehouse
Production line
Office
Branch
Distribution center
Source location (optional): allows you to associate the new location as a sublocation of an existing one.
Sublocations and hierarchical structure
Each location can have sublocations, allowing you to build hierarchical structures.
For example:
Company
Plant
Production line
Users will only be able to view and use locations for which they have been granted permissions.
👉 Contact information
For each location, you can add additional information such as:
Phone number
Description
Contact email addresses (you can enter multiple emails, separated by commas or by pressing Enter)
This information is useful for centralizing relevant location data.
👉 Location address
Locations allow you to define a geographic location using an interactive map.
You can:
Search for the address manually or by coordinates.
Adjust the location directly on the map.
Save information such as:
Address
City
State or region
Country
Postal code
This information can be used in reports and to better contextualize records.
📍 Using Locations in other modules
Locations are integrated with different DataScope modules:
👉 Forms
In list-type questions, you can associate Locations.
When answering a form, users can select the corresponding location.
👉 Home and filters
In the Home section, you can filter records by Location.
This allows you to quickly view information related to a specific location
👉 Issues, Tasks, Assets, and other modules
Locations can be associated with issues, tasks, assets, and other modules that use lists.
This improves traceability and location-based analysis.
🔐 Location permissions and restrictions
The permissions configured for Locations allow you to control two important aspects:
Which locations each user can view and select within the platform and mobile app.
Which responses a user can view according to the location associated with the response.
This means that:
If a user does not have access to a specific location, that location will not appear as an available option.
Additionally, the user will not be able to view responses related to locations they do not have permission to access.
These restrictions help keep information segmented and secure according to the assigned operation, branch, plant, or area.
📌 Coexistence with the previous version
During a transition period, the new Locations version will coexist with the previous version.
We recommend starting to use this new experience to become familiar with its improvements and to support a gradual migration.
Best practices
Define a clear structure before creating many locations.
Use sublocations to reflect your operational reality.
Keep contact and location information up to date.
Review user permissions to ensure proper access.