Setting Up Child Sites

Child sites are a tool for organizing your Files.com footprint. Because they are intended to meet long-term or permanent organization needs, creating new child sites is restricted to Site Administrators of a parent site.

Creating Child Sites

Child sites are fully-functional sites, with all of the ancillary features that entails, including DNS records, IP addresses, SSO identity provider integrations, Remote Server integrations, API Keys, Users, Groups, Automations, and every other object that can belong to a site.

Creating a child site is designed to be as effortless as possible, but it requires manual effort by a Site Administrator, and it cannot be automated using any of our SDKs or CLI. We do this to protect the quality of our service because of the overhead involved in creating a new site.

New child sites can only be created through the web interface by a Site Administrator. Each child site offers the same level of features provided by your primary site's plan. The usage of all your child sites is included in your total usage calculations.

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

Maximum Number of Child Sites

If your plan allows child sites, you will only be able to create a limited number of child sites. When you've reached the maximum, you can't create a new child site. If you need additional child sites, feel free to get in touch with our support team.

If your plan does not include complimentary child sites, contact our sales team to upgrade to a plan that does.

Child Sites Cannot Have Child Sites

Child sites are designed to enforce hard boundaries that reflect organizational patterns which require incompatible site-wide settings. They are not intended to represent matrix hierarchies of organization. This results in a few, simple restrictions:

• Your Files.com account may have only 1 parent site, and all of your other sites are child sites of that parent site.
• You cannot create multiple, nested "levels" of child sites, e.g., a child site of a child site.
• All child sites belong to exactly 1 parent site; they cannot have multiple parent sites.

We have found these restrictions provide enough flexibility for every arrangement our customers have proposed without introducing unnecessary confusion.

Default Values for Child Site Settings

Child Site Management Policies let you "lock down" settings for your child sites. This means you can define settings within the parent site that are automatically applied to child sites, and those settings cannot be changed within the child site.

Removing Child Sites

Child sites are permanent structures, so Site Administrators must manually request their removal. Contact Files.com support to remove a child site.

Child Site Usage Statistics

We combine the usage statistics of all child sites with that of the parent site for calculating overages. Billable users, API calls, and data transferred or stored across both parent and child sites is aggregated to determine total usage. By consolidating usage in this way, we ensure a more accurate reflection of overall activity within an organization’s site hierarchy, so your billing is transparent and consistent.