Slice Security - Data Cell Access

I am not positive but typically I start with the first slice by either a) removing all access to all users, then slowing adding it back slice by slice or b) grant all users access then removing it from only select slices of users.

For example if your first slice is like this which would be A)

Then subsequent slices would add back or increase U1 access for different BUs like this:

So in a sense choosing Apply vs Increase vs Decrease may depend on what you have granted in prior or subsequent slices.

I typically start by removing access (Apply No Access) for "Everyone" then in then in the next slice increase access for anyone that has READ or WRITE to everything (Increase to Read Only or All Access then continue) in the UD. Then follow up for people who are not in the "everything" meaning they currently have no rights (per first slice) and are not allowed to read or write everything (3rd slice) start adding back in different slices based on different user groups (Increase to Read Only or All Access for a subset of the UD) and so on.

Not sure if that helps but I think Apply vs Increase vs Decrease is in relation to prior or subsequent steps.

Agreed with Teresa. It should be relevant to prior steps. For example, the 1st row in the slice access applies "No Access" to U8#Grandparent.Base. The 2nd row applies "All Access" to U8#Child1. Then, on the 3rd row, if we increase access to "Read Only" on U8#Parent.Base. Assume all 3 rows will be evaluated, and nothing stop in the middle of evaluation. Then Child1 now is still All access, because All access cannot be increased to Read only. However, all other children will be "Read only" because they are originally "No Access", and can be increased to "Read only".

Please correct if I am wrong. I think the combination of "Increase access" with "No Access" and "Decrease access" with "All Access" do not make sense. How can we increase access to no access or decrease access to all access? These two combinations should never work. 

Kai