| Territory table | 
The Territory table allows you to retrieve the territories defined for an organization. A territory designates a collection of customers, depots, drivers, and vehicles.
|  Note | 
|---|
| This table supports Response integrations for Fleet accounts. | 
This topic contains the following sections:
 Requirements
RequirementsWhen you write templates that access this table, follow these requirements:
Specify the Symbolic Name for the table version to use:
TableID = Territory-1.0
Specify an Intent that this table supports:
Input templates: In your [Output] section, be sure to map an input value to every table column that is flagged as being a primary key or required.
[Filter] Id(ExtId) = Equals(Id1) # You can filter on literals or on variables from the [User] or [Calculated] sections.
[Filter] Id(ExtId) = In(["Id1","Id2","Id3"])
 Territory column descriptions
Territory column descriptionsThis list includes each column's name, which you use in expressions to retrieve data, and data type, which defines how the data is retrieved.
| Column | Data Type | Description | 
|---|---|---|
| Id | Id | (primary key) The Id of the territory. | 
| Name | Text | (Telogis key) The name of the territory. | 
| TimeZone | Text | The timezone in which the territory is located. | 
Additional columns:
 Custom columns
Custom columns| Column | Data Type | Description | 
|---|---|---|
| Custom.name | Text | Specifies a user-defined custom column name to store additional information in the table. If the column name contains non-alphanumeric characters, enclose the value in brackets, for example Custom.[Special column]. |