Creating a Child Site

This page covers creating a new Child Site. See Child Sites for an overview of what Child Sites are and when to use them.

Only Parent Site Administrators can create Child Sites, and creation happens only through the Web Interface. Provisioning a Child Site stands up a fully separate site, including DNS records, certificates, IP allocation, and a new database tenant, which is why it cannot be automated through the API, SDKs, CLI, or Terraform.

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.

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.

Plan Limits

Child Sites require a qualifying plan. Within that plan, the number of Child Sites you can create is capped. When you reach the cap, creating an additional Child Site is blocked. Contact support for more capacity. If your current plan does not include Child Sites, contact sales to upgrade to a plan that does.

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

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.