Purpose
The Offices tab stores a list of a firm's offices. These office entries records are used elsewhere in the application. Examples include...
- Defining the office a user is associated with (Users)
- Storing a project's owning office (Project Specifications)
- Displaying an office location on a client report under the company logo (required per ASTM)
- Filtering the Dashboard to just projects belonging to a specific office (requires an owning office be defined in Project Specifications)
- Qualifying Activity Log default text libraries to a specific office location
Offices
| Code | - Short code for the office
- 10 characters allowed
|
| External ID | - ID from your source system if your adapter brings over Offices
|
| Name | - Long name of the office
- Required
|
| Address 1 | |
| Address 2 | |
| City | |
| State / Province | - Office state / province
- Required
|
ZIP ZIP
Image Removed
...
|
| Region | - Geographic region the office is associated with
|
| Report Logo | - Optional logo file specific to an office location
- If logo exists for the office, the office logo will be used instead of the global default logo file
| Warning |
|---|
| If you are using FireFox there is a known issue preventing the uploading of files. You will need to use a different browser, such as Chrome or Internet Explorer, to perform this function. |
|
| Include Name on Reports | - Indicates if the name of the office will appear on reports as part of the address
|
| Info |
|---|
The Global office location is not editable. It is used in certain areas to define a value that is applicable to all office locations at a firm. Certain functionality exists that limits selections of values based on the office location / office that owns and manages the project. |