Bureaucrats, push, push-admin, push-director, push-manager, push-senior, Administrators
340
edits
Jump Freight Service: Difference between revisions
Jump to navigation
Jump to search
→Losing JF Permissions Due to Inactivity
HairyFaerie (talk | contribs) |
Xye Zaloris (talk | contribs) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 10: | Line 10: | ||
# JF contracts with less than 12 hours remaining | # JF contracts with less than 12 hours remaining | ||
# Standard contracts with less than 12 hours remaining | # Standard contracts with less than 12 hours remaining | ||
# JF contracts | # JF Rush contracts | ||
===JF Queue Priority Exceptions=== | ===JF Queue Priority Exceptions=== | ||
| Line 56: | Line 56: | ||
== Losing JF Permissions Due to Inactivity == | == Losing JF Permissions Due to Inactivity == | ||
*After | *After 21 days without completing a JF Contract, JF Pushers will lose their JF Team Permissions in PIR | ||
*When JF Team Permissions in PIR are lost, JF Pushers will be removed from the JF Team and lose their JF Team Permissions - this includes PushX SOV ACL access and JF Team communication channels. | *When JF Team Permissions in PIR are lost, JF Pushers will be removed from the JF Team and lose their JF Team Permissions - this includes PushX SOV ACL access and JF Team communication channels. | ||
*In order to rejoin the JF Team, Pushers must reapply and wait in the same Applicant Queue as other applicants. This may not require retaking the JF Team Application Interview. | *In order to rejoin the JF Team, Pushers must reapply and wait in the same Applicant Queue as other applicants. This may not require retaking the JF Team Application Interview. | ||