Optionally, the allowlist should not be considered a requirement. The reason being that it is impossible to create the following gating rule: meet all of the token threshold requirements OR be in the allowlist.

The downside with excluding the allowlist from the requirements is that you cannot apply token threshold requirements to allow listed users i.e. you can't do: meet any number of token threshold requirements AND be in the allowlist.

It seems to me that the allowlist is better utilized as a whitelist like in the OR case where token threshold requirements never apply to whitelisted members but growth/product would know best here.

agree with @timolegros here that the Allowlist should not be considered a requirement, probably need to be communicated better in the UI. @sssssabinaaa likely need your input here

agree with @timolegros here that the Allowlist should not be considered a requirement, probably need to be communicated better in the UI. @sssssabinaaa likely need your input here

If the allowlist should not be considered part of the requirements then I don't think we need any UI changes. In fact the copy above the allow list settings already indicates that it is not part of the requirements (we could maybe update "conditions' to "requirements" to make it more clear).

to reduce confusion the "necessary requirements" section should be above the section with the ERC token selection

Aight so @Israellund this is a 2fer:

1. UI change
2. Update gating func on backend to exclude allow list from number of requirements check.

@timolegros @sssssabinaaa @sachben91 🫡