Cluster administrators inevitably need to cut off some or all access to the hosted domains within a cluster when a managed service provider deploys Gateway. This can be due to non-payment or if a client uses too much storage and must clean up space before writing new content.

Access to a domain is controlled from the root Policy configuration file and the domain's policy attribute. These examples use the policy attribute of a domain for controlling access. Recall the statements in an access Policy that has an optional Sid field. Administrators use the Sid field to track the statements and to identify them for future removal when injecting statements into an existing Policy.

No Access

In this example, a domain that has “Allow” access for the domain administrator (one of the end-users) completely cuts off access to all end-users by adding the deny statements. The new statements use the Sid field to identify them for easy removal in the future.

Read-Only Access

In this example, a domain is changed to read-only mode to prevent writing, updating, or deleting content from the end-users. The new policy statement uses the Sid field to identify it for future removal. This example also uses “NotAction” to specify if the deny pertains to any action not listed thus allowing actions that are listed.

Read-Only and Delete-Only Access

A cluster administrator can set the access control policy on a domain to read and delete only if a tenant exceeds the quota. By letting the end-users continue to read and delete content, a cluster administrator uses the content already written and cleans-up content to reduce storage usage. NotAction is used to specify if deny pertains to any action not listed.