Employee Role - PosiEd

Employee Role - User/Account/Contact Record Automations

Staff members are primarily managed in PosiEd through the Employee Role object. For example when the LISS Publish Staff API is executed, records will be created in this object. 

It is important to know that the Employee Role record must have a reference to a valid Salesforce user record in order to support various functions within PosiEd. This means that regardless of how the Employee Role has been populated, you must ensure that equivalent user records are created and associated with each of these Employee Role records. Without this the system cannot have a user reference for a variety of objects including event and cohort member and can cause system errors. 

Every staff member who requires calendar access must have a user record that is licenced to support Event object entries i.e. calendar entries. Other licence types can be used for non-calendar staff e.g. a general admin person could potentially use a Chatter licence. 

A Chatter license will have this error when doing a Generate Attendance.

Open

For more information about Salesforce licencing types, please refer to your PosiEd or Salesforce consultant.

In addition to the Employee Role/user relationship, there are generally relationships established between the Employee Role and the Education Cloud Employee object and/or the Contact/Account objects.  

By default PosiEd provides automation to support the latter and these automations use similar rules to the student record/account automations. Please refer to the following:

Note that these automations have been provided as unmanaged code to allow the client to customise and meet their own requirements. For example, your school might have different standards with regards to fields such as third name, nickname and legal name etc. PosiEd allows you to define these fields for yourself on the contact/account objects and extend the automations to ensure they are populated to and from the student record as required.