Skip to content

Commit

Permalink
Update website/docs/targeting/targeting-rules/user-condition.md
Browse files Browse the repository at this point in the history
Co-authored-by: adams85 <[email protected]>
  • Loading branch information
sigewuzhere and adams85 authored Jan 19, 2024
1 parent 090495e commit 9127094
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion website/docs/targeting/targeting-rules/user-condition.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,9 @@ In this case, the feature flag evaluation is performed using the SHA256 hashes o
| NOT STARTS WITH ANY OF (hashed) | It matches when the comparison attribute does not start with any of the comparison values. |
| NOT ENDS WITH ANY OF (hashed) | It matches when the comparison attribute does not end with any of the comparison values. |

Since confidential text comparators don't support CONTAINS or DOES NOT CONTAIN comparisons, here is an example of how to target users from the same company. Which used to be handled by a rule like:
##### CONTAINS / NOT CONTAINS for confidential text

Since confidential text comparators don't support CONTAINS or NOT CONTAINS comparisons, here is an example of how to target users from the same company. Instead of defining a rule like:

<img src="/docs/assets/sensitive2.png" className="zoomable" alt="Confidential" />

Expand Down

0 comments on commit 9127094

Please sign in to comment.