The system uses a multi-layered approach to filter content based on tenant selections:
- User sees ALL records that have no tenant selections
- User sees ALL records where tenant custom attributes don't exist
- User does NOT see records that have specific tenant selections
- This ensures backward compatibility while protecting tenant-specific content
- User sees records matching their assigned tenants
- User sees records with no tenant selections (behaves like ALL selections)
- System filter applies tenant-based security to front-end content
- NO selections = ALL selections for standard modules without tenant attributes
- Records with tenant selections are only visible to users with matching tenant access
- Hard-coded audience filters must use SystemFilter scripts to respect tenant rules
- Performance impact should be considered when implementing tenant filtration
- Tenant custom attributes must be added to all modules requiring filtration
- DataId Attributes module must be configured for tenant attributes
- User/Audience Properties must be properly configured for tenant assignments