Object Definition Security
All of the object definitions have related objects in the TeamConnect Instance. The Security tab allows you to set security and restrictions for the custom objects' records and to their related records such as tasks and appointments.
By default, the security of related objects is not inherited from the parent object. Therefore it is important to use the security tab in the object definition to set which child and related objects should inherit security from the parent.
Related Object Security
Under Related Object Security section , admins can select records to inherit the record level security to the specified objects, from the Object definitions. This can be done by marking the check boxes against the records and uncheck the checkbox to remove the previously applied securities. If child custom objects are added to the parent object, then they will appear in this list in addition to the system objects.
Note: Invoices are not in the related object security list. The reason is that TeamConnect supports multi-matter invoices so it is not possible to cascade security to the invoice. Therefore automating security on invoices must be done with rules.
Other Restrictions
In the Object definitions, admins can set security access to objects if the matter is set to read-only access. For example, if a user has Read access to a matter, can they create or complete tasks for the matter.
For more information on Setting up matter security on a record, please refer to this article Working with record security. It is generally considered to be a best practice to have rules in place that set the security on matters and leverage the related object security to have match security on related objects.