Set security by location (asset)

In the location/asset hierarchy, all locations are also considered assets.

When you set up solutions and data (tags, content, dashboards) for your team, you can set security constraints by location (asset). This is beneficial for two reasons:

• Users see only the data they need.
  Instead of a long list of data that includes some irrelevant information, users see only data related to their own location (asset).

  Note: A single user can be assigned access to more than one location (asset). See Assign roles to groups.

• Data stays secure.
  Data is visible only to people with permission to see and use it.

  Note: Location (asset) can be applied to standard user accounts, but not to administrator accounts. Administrators have access to data for all locations.

You can set locations to meet the specific needs of your organization. See Location examples.

To set security by location for your team

1. Define the location/asset hierarchy you want to use for your team and data. See details.

2. For tags, from the Data Sources page, assign the appropriate location to all unassigned tags. See details.

   Or, from the tag dictionary, assign or edit location per tag. See details.

3. For equipment, include the equipment's location in the equipment CSV import file. See details.

4. From the User Management page, assign the appropriate location (asset) to each user account using the Asset Name field. See details.