As the title says, what is the relationship between these two settings?  Does Force Disassociation's "predefined threshold" come from the RSSI Threshold setting, or is it its own indepedent value?  If RSSI is not set, then does Force Disassociation work?

L.M. already asked this question in another thread but never received an answer: https://community.tp-link.com/en/business/forum/topic/204310

"Force-disassociation"
The OC200 dynamically monitors the link quality of every associated client. When the client’s current link quality drops below the predefined threshold and there are some other APs with better signal, the current AP issues an 11v roaming suggestion to the client.
With Force-disassociation disabled, the AP only issues a roaming suggestion, but whether to roam or not is determined by the client.
With Force-disassociation enabled, the AP not only issues a roaming suggestion but also disassociates the client after a while. Thus the client is supported to re-associate to a better AP. This function is recommended when there are sticky clients that don‘t roam.
 

^ I understand that and it is enabled, but the doc says about 'the predefined threshold’, so what is the level of this threshold? There is nothing more at the docs.

2) AP Load Balance

"RSSI Threshold”
Enable this function and enter the threshold of RSSI (Received Signal Strength Indication). When the clients' signal is weaker than the RSSI Threshold you've set, the clients will be disconnected from the EAP. 

I understand that feature (enabled and set for tests -70 level), but have two questions:

a) what happen when user will not have any more ap with better signal, and exceed the threshold set on the ap? will the oc200/ap disconnect the user?

b) is this function connected with the "Force-disassociation" feature? In other words, is it 'that' threshold which is being used by "Force-disassociation" feature?

If the "Force-disassociation" does not depends on "RSSI Threshold”, then which of them has a higher prio?