Design the Conditions for Data Access Sets

You can create conditions for data security using different entities. You can set conditions first and enable data security later.

Here are the things you think about when you’re creating conditions for data access sets:

• Provide read or write access to the users when you define conditions for your data access set.
• Conditions are not bound to a data access set. They are bound to an entity. Create conditions and use them in multiple data access sets.
• Delete one or more existing conditions for a selected entity. However, you can’t delete a condition already assigned to a data access set.
• Create multiple conditions for an entity in a data access set but assign only one condition to a data access set.
• Data security applies with AND condition when you select entities within a data access set and with OR condition when you select entities across various access sets.

Here are the entities using which you can create conditions:

Entity	What attributes you’re using to create conditions
Item	Hierarchy and level, such as category
Organization	Business unit, legal entity, geographical zone, and so on
Customer	Customer account, customer class, and customer site
Supplier	Seeded customer hierarchy and its associated levels
Measure Group	Measures and measure groups
Sales Organization	Sales representatives and sales team. Applicable only to the Sales and Operations module.
Segment Group	Segments

Note: Enabling security using segment group does not apply to Global Order Promising and Backlog Management modules and Bill of Resources, Audit Trail, and View Collected Measure pages.