PLS-4C: Tag Applicability Logic (AND, OR, Exclude)
Last updated: October 7, 2026
Overview
Tag applicability logic controls who can access housing cycles, meal plans, and room selection phases. By combining AND, OR, and Exclude logic, you create precise access control rules that ensure only eligible students see and interact with specific housing options.
Duration: 10 minutes
What you'll learn: How AND logic requires all tags, how OR logic requires at least one tag, how Exclude logic blocks access, and how to combine all three for complex access control.
Prerequisites: Complete 📄 PLS-4B: Applying Tags: Manual, Bulk, Forms, and Profile Fields
What Is Applicability Logic?
Applicability logic uses student tags to determine visibility and access. When you configure a housing cycle, meal plan, or room selection phase, you can set tag requirements that control which students can see and use that feature.
Where applicability logic is used:
Housing cycle access (who can apply for this cycle)
Room selection phases (who can select during this phase)
Meal plan options (which students can select this meal plan)
Move-in/move-out time slots (who can sign up for this time)
Cycles and Phases Use Profile Tags Only: Housing cycle and room selection phase applicability checks read profile tags only, NOT application tags.
Why? Application tags are frozen snapshots from when a student submitted their application. If a student's situation changes mid-cycle (they join the honors program, their financial hold is cleared, their class year updates via SIS sync), their profile tags update automatically but their application tags remain frozen. Cycles and phases need to check current student status, so they only read profile tags.
Exception: Meal plan applicability checks BOTH profile and application tags combined, since meal plan choices may depend on both current student status and preferences captured during application.
The Three Logic Types
AND Logic: Students Must Have ALL Tags
How it works: Students must have every tag in the AND list to access the feature.
When to use: When multiple requirements must all be met simultaneously.
Example: Early housing selection phase for Honors Athletes
Applicability AND: "Honors Program" + "Athlete"
Result: Only students with BOTH tags can access this phase
Student with only "Honors Program" → Cannot access
Student with only "Athlete" → Cannot access
Student with both "Honors Program" AND "Athlete" → Can access
OR Logic: Students Must Have AT LEAST ONE Tag
How it works: Students need any one tag from the OR list to access the feature.
When to use: When any of several qualifications grants access.
Example: General room selection phase for upperclass students
Applicability OR: "Class Year: Sophomore" + "Class Year: Junior" + "Class Year: Senior"
Result: Students with ANY of these tags can access
Student with "Sophomore" tag → Can access
Student with "Junior" tag → Can access
Student with no class year tags → Cannot access
Exclude Logic: Students with ANY Tag Are Blocked
How it works: Students with any tag in the Exclude list are blocked from access, even if they meet AND/OR requirements.
When to use: Blocking students who shouldn't have access (financial holds, disciplinary issues, special populations).
Example: First-year housing cycle with financial holds excluded
Applicability AND: "Class Year: First-Year"
Exclusion: "Financial Hold"
Result: First-years can access UNLESS they have a financial hold
First-year without financial hold → Can access
First-year with financial hold → Cannot access (blocked by exclusion)
Exclusions Override Everything: Exclude logic is evaluated last and overrides AND/OR logic. Even if a student meets all AND/OR requirements, a single exclusion tag will block their access.
Combining AND, OR, and Exclude Logic
The real power comes from combining all three logic types. All three are evaluated together to determine final access.
Evaluation Order
Check AND requirements → Student must have ALL tags in AND list
Check OR requirements → Student must have AT LEAST ONE tag in OR list
Check Exclusions → Student must NOT have ANY tag in Exclude list
If all checks pass → Student can access
If any check fails → Student cannot access
Example: Priority Housing for Athletes and Honors Students
Configuration:
Applicability AND: None
Applicability OR: "Housing Priority: Athlete" + "Housing Priority: Honors Program"
Exclusion: "Financial Hold" + "Disciplinary Probation"
Who can access:
Athlete without holds → YES (has OR tag, no exclusions)
Honors student without holds → YES (has OR tag, no exclusions)
Regular student → NO (no OR tags)
Athlete with financial hold → NO (has OR tag but blocked by exclusion)
Honors student on probation → NO (has OR tag but blocked by exclusion)
Example: Commuter Meal Plan for Upperclass Commuters
Configuration:
Applicability AND: "Housing Status: Commuter"
Applicability OR: "Class Year: Sophomore" + "Class Year: Junior" + "Class Year: Senior" + "Class Year: Graduate"
Exclusion: "Meal Plan: Full Board" (students already on full board can't downgrade to commuter plan)
Who can access:
Sophomore commuter without meal plan → YES
Junior commuter without meal plan → YES
First-year commuter → NO (doesn't meet OR requirements)
Sophomore resident (not commuter) → NO (doesn't meet AND requirements)
Sophomore commuter already on full board → NO (blocked by exclusion)
Formula: Access = (Has ALL AND tags) AND (Has AT LEAST ONE OR tag) AND (Has ZERO Exclude tags)
Configuring Applicability on Housing Cycles
Cycle-Level Applicability
Controls who can see and apply for the entire housing cycle.
Step 1: Navigate to Setup → Cycles
Step 2: Open your cycle or create a new one
Step 3: In the cycle settings, configure:
Applicability Tags (AND): Add tags students must ALL have
Applicability Tags (OR): Add tags where students need AT LEAST ONE
Exclusion Tags: Add tags that block access
Step 4: Save the cycle
Result: Only students meeting these tag requirements will see this cycle in their portal.
Phase-Level Applicability
Controls who can participate in specific room selection phases within a cycle.
Step 1: Open a housing cycle
Step 2: Navigate to Phases
Step 3: Create or edit a Room Selection phase
Step 4: Configure phase applicability:
Applicability AND tags
Applicability OR tags
Exclusion tags
Step 5: Save the phase
Result: Only students meeting these requirements can select rooms during this phase.
Layered Access Control: Students must meet both cycle-level AND phase-level requirements. If a cycle requires "First-Year" tag and a phase requires "Honors Program" tag, students need BOTH tags to select during that phase.
Configuring Applicability on Meal Plans
Step 1: Navigate to meal plan configuration (within a cycle or globally)
Step 2: Create or edit a meal plan option
Step 3: Configure applicability:
Applicability Tags (AND): Students must have ALL these tags
Exclusion Tags: Students with ANY of these tags cannot select this plan
Step 4: Save the meal plan
Result: Only eligible students see this meal plan option during meal plan selection.
Example: Commuter meal plan
Applicability AND: "Housing Status: Commuter"
Result: Only commuter students see this option
Real-World Applicability Scenarios
Scenario 1: First-Year Housing Cycle
Goal: Only first-years can apply, but exclude students with financial holds.
Configuration:
Applicability AND: "Class Year: First-Year"
Applicability OR: None
Exclusion: "Financial Hold"
Result: First-year students without financial holds can access the cycle.
Scenario 2: Honors Housing Phase with Priority Tiers
Goal: Phase 1 is for returning honors residents, Phase 2 is for all honors students.
Phase 1 Configuration:
Applicability AND: "Honors Program" + "Housing Status: Returning Resident"
Dates: March 1-7
Phase 2 Configuration:
Applicability AND: "Honors Program"
Dates: March 8-15
Result: Returning honors residents select first, then all honors students select.
Scenario 3: Move-Out Time Slots by Class Year
Goal: Seniors move out first, then juniors, then sophomores.
Time Slot 1 (May 1-3):
Applicability AND: "Class Year: Senior"
Time Slot 2 (May 4-6):
Applicability AND: "Class Year: Junior"
Time Slot 3 (May 7-9):
Applicability AND: "Class Year: Sophomore"
Result: Each class year only sees their designated move-out time slots.
Scenario 4: Athlete Early Selection with Fallback
Goal: Athletes select early, but if they don't select during their phase, they can select during general selection.
Phase 1 - Athlete Priority (Feb 1-7):
Applicability AND: "Housing Priority: Athlete"
Phase 2 - General Selection (Feb 8-28):
Applicability OR: "Class Year: Sophomore" + "Class Year: Junior" + "Class Year: Senior"
Exclusion: None
Result: Athletes can select in Phase 1. If they miss Phase 1, they can still select in Phase 2 (as long as they meet the OR requirements).
Common Mistakes and How to Fix Them
Mistake 1: Tags Only on Applications, Not Profiles
Symptom: You created a tag called "Application Completed - Fall 2025" and added it to students' applications. You then tried to exclude students with this tag from accessing a waitlist cycle, but the exclusion doesn't work.
Cause: Cycle and phase applicability checks read tags from student profiles only. If a tag only exists on the application record (not the profile), it won't affect cycle or phase access.
Why this happens: Application tags are frozen snapshots from submission time. Cycles and phases need to check current student eligibility, so they only read profile tags that stay up-to-date.
Fix: Copy the tag to student profiles:
Navigate to Applications
Filter by the application tag: "Application Completed - Fall 2025"
Export the list and copy Student IDs
Navigate to Profiles
Filter by those Student IDs
Bulk-add the same tag to their profiles
Now the cycle exclusion will work
Remember: For cycle and phase access control, always add tags to profiles. For meal plan access control, tags on either profiles or applications will work (meal plans check both).
Mistake 2: Confusing AND vs OR Logic
Symptom: Too many or too few students can access a phase.
Cause: AND logic is more restrictive (requires ALL tags). OR logic is more permissive (requires ANY tag).
Fix: Ask yourself: "Do students need ALL these qualifications (AND) or just ONE qualification (OR)?"
Mistake 3: Forgetting Exclusions Override Everything
Symptom: Students who should qualify are blocked from access.
Cause: An exclusion tag is blocking them, even though they meet AND/OR requirements.
Fix: Check the exclusion tag list. Remove or review tags that might be blocking eligible students.
Mistake 4: Move-In Time Slots Use AND Logic, Not OR
Symptom: You want athletes OR honors students to sign up for a move-in time slot, but only students with BOTH tags can sign up.
Cause: Move-in time slot tags use AND logic. If you add multiple tags, students need ALL of them.
Fix: Create separate time slots for each tag group:
Time Slot 1: Athletes only
Time Slot 2: Honors students only
Both time slots can have identical dates/times - functionally this creates OR logic for students.
Test Your Applicability: Create test student profiles with different tag combinations and verify which cycles/phases they can see. Testing prevents surprises during go-live.
What's Next
You've learned how to control access using AND, OR, and Exclude logic. Next, you'll learn how to build rulesets that use tags to automate roommate matching and enforce housing policies.
Continue to: PLS-4D: Building Rulesets for Roommate Matching