Ban/Warning list

[tskeeley]

Story:
The organisation board chooses to set an overall ban on an attendee, or make it that an attendee needs to be talked to by an Operations official before they are allowed to attend an event.

Effects:

• Any director needs to be able to set and remove a ban on an attendee. Doing so sends an email to the board with the particulars. An email is also sent to Registration heads and Operation Heads that a ban was added or removed, but no details are included (see below about Operations access to details)

• • If the attendee already has a membership at time of ban, the director needs to be able choose if the membership is refunded (email to reg and CFO) or not.
• • When the ban/warn flag is removed, the particulars of when the ban/warn was placed, and why it was need to be maintained in a field only view-able by the heads of Operations and directors

• The user should not be allowed to register or pick up a badge while a flag is in place.

• The heads/subheads/specialists(?) of Registration need be able to see if it is a ban or a "warning needed", but do not need details of why.

• The heads/subheads/specialists(?) of Operations need to be able to see the details of a warning. They also need to be able to clear the warning flag after the warning is given. An email needs to be sent to Operations, Registration, and the board that the warning was issued and include the particulars of the reason for the warning and who cleared the flag.

• The heads/subheads/specialists(?) of Operations need to be able to see the details of why a ban is in place but NOT be able to remove the ban flag.

• Sign In Portal access workflow change:

• • If a user has the ban flag, they cannot access portal. A message directing them to contact the board should display.
• • If a server has the warning flag, they CAN access portal, but the main page and registration page needs to show that they need to contact and Operations Head or Subhead before they will be allowed to pick up their badge.

[mshappe]

Per discussion this afternoon, thinking three categories:

• "Black" list: may not register.
• "Brown" list: may register but will need a "talk" before a badge is actually handed to them.
• "Grey" list: may register and there is some explicit notification to key people that they have, but no impediment to their picking up a badge.

[AricStewart]

Do you want this as a "list", or a flag on an account, or do you not care about the implementation and just want "Mark an account for reason 'A' and have ramifications XYZ"

[tskeeley]

Flag please. And you might want to include this in a "pickup limitation" flag, for things like, "they have to settle up with ArtShow before they can pickup their badge (similar to Brown, but not operations specific (or brown can be directed, instead of just "the talk")