...

• At the highest prioirty level (Priority 1), Zone[1] can shut off all outbound data record changes to Zone[2]. At the lowest priority level (Prioirty 5), Zone[1] can shut off sharing a single attribute on a single adaptor (that it owns) to Zone[2].
• Sharing precedence is based on the priority e.g. If Zone[1] has turned off access to Zone[2] (Priority 1), then all other sharing actions are null.
• Permissions for each element are based on REST operations GET, PATCH, POST and DELETE. An additional operation is added for PUSH, where a zone allows another zone to receive real-time changes. However, it may be determined that GET will scope will include PUSH.

Inbound ACLs

...

A zone or adaptor has the capability of filtering out changes it has scope acess to.

• "forbid" zone: Don't GET or accept any updates from a zone
• "forbid" adaptor: Don't GET or accept any updates from an adaptor

...