# Segments: Allow segments to use OR operations for defining identity criteria **URL:** \ **Category:** Idea Discussions\ **Tags:** segments, identity-security-cloud\ **Created:** [September 10, 2024, 3:28pm UTC](https://developer.sailpoint.com/discuss/t/segments-allow-segments-to-use-or-operations-for-defining-identity-criteria/80760 "2024-09-10T15:28:36Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![gmilunich](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gmilunich/32/8431_2.png) [@gmilunich](https://developer.sailpoint.com/discuss/u/gmilunich)\ **Post date:** [September 10, 2024, 3:28pm UTC](https://developer.sailpoint.com/discuss/t/segments-allow-segments-to-use-or-operations-for-defining-identity-criteria/80760/1 "2024-09-10T15:28:36Z")
When defining the identity membership criteria for segments, the only option for operations between attributes is “AND”. There is an additional limitation because of this that the IdentityAttribute can only be specified once (as expected with AND-only.) However, in the real world, a Segment may be made up of people who have differing values for a field. Having the ability to add OR clauses for IdentityAttributes selected would be beneficial, and reduce the need for duplicating segments. The OR clause could be handled in the same manner that Campaign Filter criteria are, where the primary operation is AND, but if you add a second option for the same IdentityAttribute, it becomes an OR for that IdentityAttribute. **Use Case:** The client is global and has an IdentityAttribute of Country that lists the country the user is in. They would like to have segments for Users in the Finance Department based in similar regions, suck as “North America”, “Europe”, “Asia”, etc. The selection criteria for the North American segment would be something like this: `( Counrty==USA OR Country==Canada OR Country==Mexico ) AND Department==Finance` Because there is no option for OR, there are 2 less-than-ideal workarounds that could be used: 1. Create a Segement per country in the region, such as “North America - USA - Finance”, North America - Canada - Finance", and “North America - Mexico - Finance”. This would then require you to duplicate all the access available for each of these. 2. Create a new IdentityAttribute for Region, and then create a Transform to calculate the Region for each user based on their country. This requires another IA, and another Transform to maintain, and is not scalable if you have several OR conditions to manage. Reference Topic: [Segments in Identity Security Cloud](https://developer.sailpoint.com/discuss/t/segments-in-identity-security-cloud/80724) ---
**Author:** ![rjamorim](https://avatars.discourse-cdn.com/v4/letter/r/7cd45c/32.png) [@rjamorim](https://developer.sailpoint.com/discuss/u/rjamorim)\ **Post date:** [September 13, 2024, 6:16pm UTC](https://developer.sailpoint.com/discuss/t/segments-allow-segments-to-use-or-operations-for-defining-identity-criteria/80760/2 "2024-09-13T18:16:03Z")
Just a heads up: this idea has been mentioned in SailPoint’s ideas portal: [https://ideas.sailpoint.com/ideas/GOV-I-2788](https://ideas.sailpoint.com/ideas/GOV-I-2788) Customers interested in this feature should consider voting for the idea and adding a comment explaining their use case, as that would raise its visibility among the product managers. ---
**Author:** ![mehuljogi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mehuljogi/32/8264_2.png) [@mehuljogi](https://developer.sailpoint.com/discuss/u/mehuljogi)\ **Post date:** [January 22, 2025, 7:22pm UTC](https://developer.sailpoint.com/discuss/t/segments-allow-segments-to-use-or-operations-for-defining-identity-criteria/80760/3 "2025-01-22T19:22:32Z")
Hi @gmilunich , You are right about creating separate segments for each country and [SailPoint documentation](https://documentation.sailpoint.com/saas/help/requests/segments.html) also suggest this methods for having OR condition between two criteria as shown below in the picture. Thanks @rjamorim for sharing this idea. I’ll also vote for this feature so it can be reflected in ISC tenants asap. ![image](https://global.discourse-cdn.com/sailpoint/original/3X/c/1/c1231732dc5fc597aed5d0caf560cdae94520f3f.png) -Mehul ---
**Author:** ![osmanmohammed](https://avatars.discourse-cdn.com/v4/letter/o/e0b2c6/32.png) [@osmanmohammed](https://developer.sailpoint.com/discuss/u/osmanmohammed)\ **Post date:** [February 11, 2025, 8:04pm UTC](https://developer.sailpoint.com/discuss/t/segments-allow-segments-to-use-or-operations-for-defining-identity-criteria/80760/4 "2025-02-11T20:04:40Z")
Hi Roberto can we use greater than / less than sign along date attribute 2025-01-01 ? ‘gt’ /‘lt’/‘ge’/‘le’ thanks osman ---
**Author:** ![Abhishek\_1995](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Abhishek\_1995](https://developer.sailpoint.com/discuss/u/Abhishek_1995)\ **Post date:** [March 13, 2025, 5:50am UTC](https://developer.sailpoint.com/discuss/t/segments-allow-segments-to-use-or-operations-for-defining-identity-criteria/80760/5 "2025-03-13T05:50:34Z")
Hi Roberto, In define segment while giving the **value** can we use **%** for example S or s%. so that i can get the user only who start from S or s only. Thank you!