| # | Header | Description | Req. | Notes |
| 1 | PrettyName | Name for the value you want to add to the Location field. | Y | Must be unique. Must be first field. Only required field in modification imports. |
| 2 | Description | Full description of the Location value. | Y | Sometimes overloaded with abbreviations or codes for payroll or billing exports. |
| 3 | AutoAdd | Is this Location value added to all new groups? | N | Must be a capital "Y" for AutoAdd. Capital "N", blank, or any other value is not AutoAdd. |
| 4 | Visibility | Loggable, reportable only, or hidden | N | The acceptable values are LR for Loggable and Reportable, RO for Reportable Only, and hide for Hidden. |
| 5 | Groups | What groups should the Location value be added to? | N | Name of each group that the Location value should be added to. Comma-delimit multiple group names in the field. |
Just as in the application itself, hiding a Location value will remove it from all Groups. If the Location was previously hidden (defined as not being a member of any Group) and gets set to either "LR" or "RO", then it is added to the All Group only (no other Groups).
The Visibility column is handled before the Groups column. This means that if you set a Location to "hide" and then go ahead and specify some Groups, first it will be hidden, and then it will be added to the specified Groups, which effectively unhides it. (Though it will still show up as "RO" on the Locations screen.) The Import Results screen will say "Location X is hidden" and then it will say "Location X added to Group Y".