Locations

Subscription Tier Required

This feature requires the Premier subscription tier or higher.

Locations represent a physical location, like a separate facility, and are used to restrict access to some entities.

Each account comes with a single location named "Location 1" pre-installed. The Location field will be hidden on most entities until multiple Locations have been created.

Settings

Field	Description
Name	Unique name of the Location.

Entities

Locations apply to the following entities. If no Location is set on the entity, it will be available to all Users and API Keys.

• Parts
• Processes
• Characteristics
• Defects
• Defect Categories

Locations also apply to Users and API Keys. Users and API Keys must have at least one Location set. If only one Location exists, it will automatically be applied when the User or API Key is created.

Access To All Locations

Roles which apply the Allow Access to All Locations permission allow Users and API Keys to access entities in any Location. In contexts where a single location is required, such as submitting data, the User may change which Location they will use in the User Settings overlay. Selecting a Location in the User Settings overlay does not restrict which Locations the User has access to. If the User wishes to fully simulate being in a single Location, they may check Impersonate Location.

Warning

When a User checks the Impersonate Location box, they may begin to receive errors indicating that they do not have permissions to access a Location. This is expected.

Import/Export

Column Header	Create	Update	Description
ID	Not Allowed	Required	Location's Internal ID
Name	Required	Optional	String

See Also

• Core Concepts: Entities
• In-Depth Guide: Using Locations