Multiple password policies for same object (ADSAccount)

Password policies can be assigned depending on foreign key relations of the object in question. For ADSAccount you can by default assign different policies depending on domain or container. Use Manager to "Assgin objects", with the Apply to select first the table you select by (ADSDomain or ADSContainer) then the actual object (OU). You can also use Designer with slightly differntly ordered fields.

It is possible to add other FK relations as selection criteria, by customizing the view (using ViewAddOns) "QBMVPwdPolicyColumns", but that is somewhat convoluted. I would suggest you talk to your implementation partner or the professional services team to help you regarding the keyword "fine-grained password policies".

Password policies can be assigned depending on foreign key relations of the object in question. For ADSAccount you can by default assign different policies depending on domain or container. Use Manager to "Assgin objects", with the Apply to select first the table you select by (ADSDomain or ADSContainer) then the actual object (OU). You can also use Designer with slightly differntly ordered fields.

It is possible to add other FK relations as selection criteria, by customizing the view (using ViewAddOns) "QBMVPwdPolicyColumns", but that is somewhat convoluted. I would suggest you talk to your implementation partner or the professional services team to help you regarding the keyword "fine-grained password policies".