The third-party contact table, vm_vdr_contact, extends the User table [sys_user]. By inheriting from sys_user, a contact receives the standard user attributes, including name, email address and credentials, as well as the capabilities of the platform's authentication and notification services. This is what allows a contact to log in to the Third-party Portal and to receive email notifications from the application.
The task table is a work item parent and has no relevance to person records. The ext_user table is not the parent of contacts. The Company table [core_company] holds organizations; the third-party record is held there, and the contact relates to it through a reference field, not by extending it.
This inheritance has implementation consequences. Contacts are subject to user-level controls such as access control rules, roles and, where configured, restrictions on internal functionality, so the integrity of their role assignments is essential to keeping them confined to the portal. Importing contacts also follows the user data model, so email addresses must be unique and valid, and administrators should confirm that the contact is linked to the correct third party before invitations are sent.
[Reference: Study Guide – Core Configuration: Third-party Contact Data Model and Table Hierarchy.]