Skip to content

Commit

Permalink
sensitive example
Browse files Browse the repository at this point in the history
  • Loading branch information
sigewuzhere committed Mar 2, 2020
1 parent c90870e commit c7d1fd1
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions docs/advanced/targeting.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,11 +58,15 @@ In this case the feature flag evaluation is based on the secure hashes of the co
| IS ONE OF (Sensitive) | Checks if the *Attribute* is listed in the *Comparison value*. *Comparison value* should be a comma separated list. |
| IS NOT ONE OF (Sensitive) | True if the *Attribute* is not listed in the *Comparison value*. |

Since sensitive text comparators don't support CONTAINS or DOES NOT CONTAIN comparisons, here is an example how to target users from the same company.
Adding a `domain` custom attribute and using only sensitive comparators to target them.
Since sensitive text comparators don't support CONTAINS or DOES NOT CONTAIN comparisons, here is an example how to target users from the same company. Which used to be handled by a rule like:

![Sensitive](assets/sensitive2.png)


You can add a custom attribute called `domain` and use only sensitive comparators in the targeting rule.

On the Dashboard:
![targeting-1](assets/sensitive1.png)
![Sensitive](assets/sensitive1.png)

In your code:
```js
Expand Down
Binary file added docs/assets/sensitive2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit c7d1fd1

Please sign in to comment.