This table holds information about the companies that interact with your organization. It may include . Each Company record is assigned a role, which is used to categorize the records, as well as determine the fields that appear on their layouts. A few examples of company roles that are included by default in the out-of-the-box system are customers, vendors, prospects, or manufacturers. As one of the more prominent background tables in the system, the Company table contains mostly static data, and thus does not have any associated workflow actions.

Company record layouts change depending on the Primary Role they are given when the record is created. This is similar to how the People table is broken down into subtables of Employees and External Users, to name a fewbut prevents the need to split the Companies table into separate subtables for Customer, Vendor, or Prospect records, etc. Record layouts change because sometimes, a certain Company Role record requires additional or different information. However, regardless of Company Role, the majority of the Company record layout stays the same.

Each Company record uses specific tabs that contain data about:

• Key Info: holds contact information, basic financial information, and some representative information of the company.
• Locations and Contacts: contains embedded tables for Location and Contact records that relate to the company.
• Sales Info: contains embedded tables for Opportunity, Quote, and Purchase Order records that relate to the company.
• Related Records: contains embedded tables for Support Case, Contract, Insurance Certificate, and Asset records that relate to the company.

Use Case

...

Company records can be created in a variety of ways:

• Passively, via the Company Name field, whenever a new record gets created in the Leads table
• By members of the Admin, Admin Import, Business Admin, Contract Creator, Contract Manager, Contract

...

• Owner, Contract

...

• Requester, Marketing, Project Manager, and Sales groups

...

• directly in the Companies table
• Directly in the Contract Party Information section of a new Contract record: by clicking the New Company radio button, filling in the necessary information, and clicking Create Company

Many other tables link to information stored in the Company table, which is partially why Company records can be created in other places, and how Company records themselves can create new records in other tables. When a new Company record is created, the address information is inputted under the Locations and Contacts tab, and then stored as an individual Location record in the Locations background table. A Company with the Parent type may have several Location records, such as one for their billing office, for branch locations, and for their headquarters. If the location in question doesn't already exist as a Location record in the system, the new Location records are created automatically when Company records are created, similar to how Company records can be created when new Lead or Contract records are created. This connectivity allows workflows to run optimally while minimizing the potential for human error. For example:

• When new Insurance Certificate records are created from the Related Records tab of the Company record, the Insurance Certificate Owner gets notified 14

Company address information is stored in the Locations background table and displayed on the Locations and Contacts tab. A parent company may have several locations, e.g., a billing office, branch locations, and headquarters.

Image Removed

...

• days before one or more certificates is due to expire, provided that there is at least one active or pending contract. The Insurance Certificate Owner's information can be found just above the Insurance Certificates embedded table.
• When new Insurance Certificate records are created from the Related Records tab of the Company record, they are automatically linked to all Contract records associated with that company.

Automation

In the certificate record, the Main Contact is the primary contact at the vendor company.

Image Removed

Insurance certificates added to a company record are automatically linked to all contracts associated with the vendor company. See the Insurance Coverages Table for more information.

Ownership of Companies

the standard system demo, the Company table contains four rules. These rules are accessed by expanding the Company table in the left pane, selecting Setup Company Documents, and then selecting the Rules tab:

Details on each rule are included in the list below:

• Create: Contract Source Actions (web, API): This rule runs whenever a new Company record is created by a user or by another rule in the system. It consists of two actions: L: Set Company ID in source contract and U: Set Company Roles. L: Set Company ID in source contract is a Linked Field action that links the ID field in a Company record to the Company ID field in a related Contract record, and U: Set Company Roles is an Update action that updates the Company Roles field with the Company Type.
• Edit: Contract Source Actions (web, API): This rule runs whenever a Contract Source ID field has been edited changed to a non-zero value. It consists of a Linked Field action called L: Set Company ID in source contract.
• TB: Notify about expiring insurance certificates (disabled): This time-based rule runs every other day at 3 AM, and contains an action called E: Email Contract Owner of Upcoming Insurance Cert Expiration. This action uses a saved search to check if any active or in-progress Insurance Certificates records are set to expire within 14 days, and then emails the Contract Owner with results. This rule is comes disabled by default.
• TB Demo Data Update: This time-based rule runs once every month, updates Demo Date fields, and deletes History. It consists of two actions: "U: Update Demo Dates' and "D: Delete History for TB: Demo Data Update." "U: Update Demo Dates" is an Update action that replaces the Date Created, Date Updated, Original Start Date, and Reference As Of fields with a date one month in the future. "D: Delete History for TB: Demo Data Update" is a Delete action that deletes history entries that are created after "U: Update Demo Dates" updates the designated fields. This is a good example of ensuring that the actions in your rules are added in proper order, otherwise the Delete action would have nothing to delete.

Ownership

Placeholder content:

Records in the Company table are owned by the individual that is named in the ID field of the Key Info tab. To view Group permissions for creating, editing, viewing, and deleting, visit the Permissions tab of the Company table wizard.

Field used to define ownership: ID

Matching field in People table: Company IDRecords in this table are "owned" by the individual assigned sales representative. Admins and members of the Contract Owner, Contract Manager, Marketing, Project Manager, and Sales groups can view and edit Companies. Most groups can view their own Company, and most internal users can view others' Companies.