Skip to content

Organization Schema

Emakin stores organisation data in a structured schema made up of multiple entities, each backed by its own database table. These tables are created automatically when a new domain is registered.

The schema can be extended with additional entities and relations, but the default structure is the one shown below.

Database diagram showing the default organization schema entities and their relations.

How to Read the Schema

The diagram contains:

  • entity boxes, which represent tables such as Users, OrganizationUnits, and Positions
  • field lists inside those boxes
  • connecting lines, which represent relations between entities
  • relation names and direction arrows
  • symbols at both ends of the relation line that indicate the relation type

See the image below for the documented relation symbols.

Legend for organization schema relation types.

Using the Schema in Membership Expressions

Relations can be traversed by using $Membership methods. For example, to get the department name of a work item's initiator user:

1
$Membership.GetProperty($Initiator, 'Employee.Department.Name')

This example follows the relations defined in the organisation schema to resolve the referenced department value.

Operational Notes

  • New domains start with the default organisation schema.
  • Additional entities and relations can be introduced when the deployment requires a richer organisation model.
  • Schema changes should be reviewed carefully because they affect how membership-based data can be queried and resolved.