Subject: Enforce Consistent ACL was primarily aimed at…
local replicas
i.e to stop users with the skills and tools available from making changes on their client that could replicate back up to the server with bad consequences for functionality
Howvere You should also be aware that Lotus also made the decision to require that Ensure Consistent ACL be ON for Roles to be available on a LOCAL replica. Thats why I nearly always have it enabled :={. (Personallly I think this dual purpose is a stupid decision but there … )
As to whether the ACL entries replicate between servers … well that can depend.
If an application is deployed in a single Notes Domain, perhaps a single organisation, then the developer usually wants ACL entries to replicate freely. So all the ACL is set up with all servers as Manager.
However in other circumstances … for example if an application is deployed in two domains …it can be different.
Lets say Organisation A creates an application that it wishes to use to share data with Organisation B.
However Organisation A (quite reasonably) need to keep control of both Design and ACL on its own servers
Conversely Organisation B will accept the design changes but needs to control the ACL of its own servers… not leqast because access will be controlled via groups in its own Domino Directory/NAB.
So in the ACL on A’s replica
A’s servers have Manager access
B’s have only Editor
but in the ACL on B’s replica
A’s server have designer access
B’s have Manager
Oncethe proper connection and cross certificates are set up, replication can happen
but since it is the ACL on the receiving server that determines what data is accepted
a) data can flows both ways
b) design can flow from A to B
but
cv) ACL moves in neither direction!
and getting back to our original point “Ensure consitent ACL” does not affect this
Though it would action within Organisation A and Organisation B … separately of course :=)
Hope this helps a bit
AJW