Items in the user interface that are associated with specific groups of fields displayed in a record.
By adding or deleting categories in a record, you can display or hide the associated sections or fields in that record. In some cases, you might need the user rights to view specific categories and the custom fields belonging to them.
Check In or Out
A way to manage files that are uploaded to the Documents screens so that only one person at a time can edit them. If a file is checked out, no other users can edit the file. When the user is done editing and checks the file in, it becomes available for check out.
A record that has a parent record. Records can have hierarchical relationships between records. One (parent) record can have multiple (child) records, whereas each child record can have only one parent.
Child records might be required to have a parent. However, parent records are not required to have child records.
Categories can also have parent-child relations.
For more details, see "Parent and Child Accounts" on page 87 and "Parent and Child Projects" on page 110.
Individuals or organizations that conduct business with your organization and in one way or another are involved in the records with which you work. For example, staff, claimants, opposing parties, witnesses, agencies, vendors, outside counsels, and so on can all be described by contact records. You specify Categories to indicate the type of contact.
Projects that are associated with and revolve around a specific contact without which they cannot exist. For example, an insurance claim record cannot be created without specifying an insured contact.
Within a contact-centric project, the contact record is displayed as a single hyperlink. It is created through a search module field and displayed in the general information section of the project.
Objects created for your organization. Unlike System Objects, they do not come standard with TeamConnect. They are created by your TeamConnect developer. Custom objects can have names used within your organization for records or files, such as matters, and policies. Within this documentation, custom objects are referred to as Projects.