Child Sites

Child sites are a separate, fully functional site under your main Files.com site, known as the parent site. Each child site runs with its own settings, users, and rules, making it easier to manage different needs across your organization. Instead of forcing everyone to follow the same setup, each child site provides its users their own space to work, without interfering with the parent site.

Child sites handle situations where different groups need different workflows or different site-wide settings. Your IT team might require strict security settings, while your marketing team prefers more flexibility, but your finance team requires specific data governance and retention settings. Perhaps your legal team is working on a sensitive M&A project that shouldn’t mix with other files. If you have multiple brands that need different storage requirements, you need to meet varying sets of regulations for compliance. Maybe you need a staging environment to safely test new processes and code. With child sites, you can give each group a separate environment that exactly fits their needs.

Files.com provides Child Sites to customers on a qualifying plan. A child site is an entirely separate site with its own subdomain. The content and settings of each child site is self-contained, but is associated with the primary account. Child sites share the user and usage quota of the parent site. Each child site has the same level of features provided by its parent site's plan.

You can manage all child sites from your parent site. Switch between sites quickly, view and interact with files, automate transfers between sites, and track usage.

Delegate administration with child sites, letting teams manage their own users and automations, while you stay in control of the overall setup. Use child site management policies to control what settings can be changed on child sites.

Site Administrators of a parent site have full access to the contents of child sites. Parent site administrators can create Automations or Syncs that are managed within the parent site and interact with child sites.

Common Use Cases

Child sites are commonly used for departmental or subsidiary organization, confidential projects such as M&A efforts, regional requirements for storage or compliance, development and staging environments, isolated environments for incompatible requirements, and warm storage or data retention archives.

For a detailed comparison of when to use child sites versus other organizational structures, see Child Sites, Workspaces, Partners, and Admin Permissions: When To Choose Each.