Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Purpose: The User table tree is used to store information about individuals who use your system.

...

...

The People table contains data about individual users of your system and individuals with whom your organization has contact or business relationships. There are two basic subtypes of Users: External Users and Employees. Most external Contacts will go in the External User table, as the Employee table tracks information that does not apply to people outside your company, such as working hours and hire date. People records normally have a link to a record in the Company table to define which Company is related to the Person. By default, People records have an embedded list of records from another table, called a related table, listing all of their Support or Helpdesk Case records (tickets).

People are considered static in that they do not change status. By default, no workflow is specified for the People table. People may be created manually by Guests, Support Staff, and members of the Professional Services, Sales staff and Admin groups. Guest record creation is enabled by default so users can create their own logins using the limited-access "register" account. Records created by the Guest login "register" are added to the "Selfregistered users" group automatically by a rule.

People may also be created as the result of a conversion from a Lead record, or may be created as part of an import from an external database such as an LDAP directory. Each  Each Person record is assigned either a Team or an individual from the Employees subtable as the "Owner".


The Employee sub-table has a rule attached to it that runs a conversion of an Employee record to the Approvals table when triggered by a field changed on the Employee record. This facilitates the Documents approval process.