Skip to main content

Creating a Child Site

Only Parent Site Administrators can create Child Sites, and creation happens only through the Web Interface.

Creating a Child Site establishes a separate environment with its own users, security policy, and configuration. It is a significant administrative event intended to happen infrequently, so creation is not offered through the API, SDKs, CLI, or Terraform as an automated workflow step.

Plan Limits

Child Sites require a qualifying plan. The included Child Site count is a billing allowance: Parent Site Administrators can create additional Child Sites beyond that count, with the excess handled through overage billing according to the plan or agreement. Reaching the included count does not block creation.

If your current plan does not include the Child Sites feature, contact sales to upgrade to a plan that does.

Reselling Child Sites is not permitted without a separate reseller agreement with Files.com.

Creating the Site

When you create a Child Site, supply a Name. The name is translated automatically into a unique subdomain for the new site.

The Child Site is provisioned immediately and has its own users, security policy, SSO, branding, and every other site-level configuration from the moment it exists. If you have a default Child Site Management Policy then the new Child Site automatically inherits the default policy, or you can manually add the new Child Site to a different Child Site Management Policy.

A new Child Site starts empty. No files, folders, users, groups, partners, automations, syncs, or integrations carry over from the Parent Site. The Child Site's administrators build out the environment from scratch.

Designating Administrators

A Child Site can be administered by a Parent Site Administrator, by a Child Site Administrator created directly in the Child Site, or by a parent-site user delegated as an administrator on the Child Site. Parent Site Administrators do not need to be designated separately on the Child Site, because they already have full access.

A Child Site does not require any administrator other than the Parent Site Administrators who already have access. Designate Child Site Administrators when you want operational responsibility for the Child Site delegated to a specific person or team.