Resources

The Faculty Handbook defines Special Faculty as "part-time faculty, adjunct faculty, visiting faculty, artists-in-residence, writers-in-residence, practitioners-in-residence, executives-in-residence, lecturers, clinical faculty, research faculty, postdoctoral fellows, or other special categories."

In IAM, we classify Special Faculty as contracted, non-tenure track faculty users. Non-paid faculty fall under the Affiliate role designation.

Special Faculty will be referred to as Adjunct in this documentation for clarity sake.

Bravura process

Data structure

  • This is an active affiliation role. Users within the validity window have active birthright entitlements.
  • Bravura enables the account based on the FIRST_WORK_DATE field in the PEBEMPL Banner table.
  • PEBEMPL's LAST_WORK_DATE will deactivate the account.
  • Adjunct's departmental role membership is based on their departmental role and determines their Active Directory FSColl and FSDept membership.
  • Due to role coupling with Faculty and Staff, Adjuncts will very rarely be the user's primary affiliation.
  • The Staff and Faculty primary affiliation roles determine the user's university access.
    • If Special Faculty (Adjunct) is displayed as the user's primary affiliation, they will likely not have access to campus resources (e.g. printing, Adobe suite, etc.).
  • Adjuncts are in the FacultyStaff OU in Google and Active Directory.

Activation

  • Academic Affairs defines an Adjunct user's first day of system access by setting the FIRST_WORK_DATE within the PEAEMPL form.
  • Adjunct access start may precede their contract start by several days.
  • A Banner process initiated by Academic Affairs sends the access notification to the user and their supervisor. Bravura is not involved in the notification.
  • Part time faculty contracts start dates coincide with the published term start (which varies per year). If contracted to instruct during the Spring, their access end date is August 31. If contracted for Fall, their access end date is January 31.

External system access

  • Adjunct access to services external to Shibboleth are the responsibility of their department and/or college administrators.
  • Banner Admin access may be requested via the Request Banner Account Options Jira form.
  • Service access (i.e. Adobe, Microsoft 365, etc.) is based on the accompanying Faculty/Staff role coupling. Loss of these primary affiliations may cause the Adjunct to lose service access.

Departure

  • Adjuncts leaving Appalachian State University notify their department chair of their last day. The chair informs Academic Affairs.
  • Academic Affairs updates the adjunct access record via PEAEMPL to give them the appropriate LAST_WORK_DATE.
  • Adjunct access will be disabled at midnight of their LAST_WORK_DATE.
  • Adjunct's LDAP account is disabled. All systems depending on single sign on (e.g. Google, Banner Self Service) will fail.
  • Adjunct's AD account is disabled. Access to any systems depending on the AD account will fail.
  • All of the user's current sessions and tokens depending on Shibboleth are reset, signing them out of all SSO associated systems.
  • Adjunct's Google account is moved into the Inactive FacultyStaff OU.
    • The Inactive OU removes email access which, in turn:
      • prevents vacation messaging,
      • removes their forward address settings, and
      • removes their account delegations.
    • Their account is removed the Global Address List preventing it appearing in autosuggestion prompts.


  • No labels