Difference between revisions of "MyRoboJackets Access Overrides"

From RoboJackets Wiki
Jump to navigation Jump to search
m (Estrat6 moved page MyRoboJackets Access Overrides to About MyRoboJackets Access Overrides without leaving a redirect)
(3 intermediate revisions by the same user not shown)
Line 18: Line 18:
 
* User access must not be active
 
* User access must not be active
 
* User must have no prior dues payments
 
* User must have no prior dues payments
* User must have no previous access override
+
* User must have no active or prior access override
 
* A future dues package (dues package with the "access end" date in the future) must exist
 
* A future dues package (dues package with the "access end" date in the future) must exist
  
Line 25: Line 25:
 
* Sign the membership agreement
 
* Sign the membership agreement
 
* Attend a team meeting
 
* Attend a team meeting
 +
** Attendance must be recorded in MyRoboJackets for it to count. See [[How to Record Attendance]].
 +
** Only teams in MyRoboJackets that have the Self-Service Override Eligible property set to true in Nova will count towards this requirement. This means that event attendance (e.g., General Interest meetings), training attendance, and Core or discipline Core attendance will '''not''' satisfy this requirement.
  
 
A user's eligibility for a self-service override is always visible on their details page in Nova in the System Access panel.  
 
A user's eligibility for a self-service override is always visible on their details page in Nova in the System Access panel.  
  
 
Self-service overrides can last between 7 and 60 days. The longest duration will occur if the next (earliest) future dues package access end date is 60 or more days in the future. The shortest duration will occur if the next future access end date is 7 or less days away.
 
Self-service overrides can last between 7 and 60 days. The longest duration will occur if the next (earliest) future dues package access end date is 60 or more days in the future. The shortest duration will occur if the next future access end date is 7 or less days away.
 +
 +
[[Category:How to Guides: Technical]]

Revision as of 22:26, 29 August 2022

Access Overrides

An access override allows someone access to (mostly electronic) RoboJackets services even though they haven't paid dues for the current semester. Typically, access overrides are provided on a case-by-case basis upon request.

Self-Service Access Overrides

See also: How to Request a Self-Service Access Override

This section describes the business logic surrounding self-service access overrides in MyRoboJackets in-depth. The how-to page linked above describes how new members can request self-service access overrides.

To prevent abuse, several criteria must be met before a user becomes eligible for a self-service override. Under normal circumstances, it should be very easy for a well-intentioned RoboJackets new member to receive a self-service override.

Self-service override criteria are divided into 2 categories: conditions and tasks. A condition is a system- or user-level property that cannot be rectified by the user alone (see list below). However, tasks can be completed by users.

Required system/user conditions:

  • User access must not be active
  • User must have no prior dues payments
  • User must have no active or prior access override
  • A future dues package (dues package with the "access end" date in the future) must exist

Required tasks:

  • Sign the membership agreement
  • Attend a team meeting
    • Attendance must be recorded in MyRoboJackets for it to count. See How to Record Attendance.
    • Only teams in MyRoboJackets that have the Self-Service Override Eligible property set to true in Nova will count towards this requirement. This means that event attendance (e.g., General Interest meetings), training attendance, and Core or discipline Core attendance will not satisfy this requirement.

A user's eligibility for a self-service override is always visible on their details page in Nova in the System Access panel.

Self-service overrides can last between 7 and 60 days. The longest duration will occur if the next (earliest) future dues package access end date is 60 or more days in the future. The shortest duration will occur if the next future access end date is 7 or less days away.