Skip to main content
Documentation

Child Site Management Policies

Child Site Management Policies let Parent Site Administrators enforce specific site settings across Child Sites. When a setting is included in a policy, the value set by the Parent Site applies to every Child Site in scope, and Child Site Administrators cannot change it. New Child Sites automatically inherit the policy. Settings not included in the policy remain under each Child Site's control.

The only policy type today is a settings policy. A Parent Site can have at most one settings policy.

When to Use a Settings Policy

Use a settings policy when your organization has requirements that Child Site Administrators must not be able to override. The driver is typically security, compliance, or data governance. Common examples:

  • If your compliance program prohibits unencrypted FTP, add the Plain/unencrypted FTP Support setting to the policy and disable it. Child Site Administrators cannot re-enable it.
  • If users across your organization must use 2FA, enforce that setting from the Parent Site so no Child Site can relax it.
  • If your data governance program requires a specific retention period, set it in the policy to prevent Child Sites from diverging.

Creating a Settings Policy

To create a settings policy, provide a Name. You can also provide a Description as a note for reference.

Define the scope of affected Child Sites. A settings policy either applies to every Child Site, or to every Child Site except a list you specify.

Add any settings you want to enforce to the policy. Each setting requires a value, and the value must be valid for that setting. Settings you do not add remain editable within each Child Site. The full list of policy-managed settings is in the developer documentationExternal LinkThis link leads to an external website and will open in a new tab.

When you save the policy, the settings take effect immediately for every Child Site in scope. New Child Sites created later automatically inherit the policy.

Settings values are saved inside the policy itself. Changing a setting on the Parent Site does not change the policy value. Edit the policy directly to change what is enforced on Child Sites.

A settings policy never restricts or changes the Parent Site's own settings.