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, also known as subsites, offer a versatile solution for managing distinct departments, subsidiaries, multiple brands of your company, or very distinct projects within a larger organizational framework.

Each child site will have access to the same level of features provided its parent site's plan, such as how often Remote Server Syncs can be triggered. Child sites share the user and usage quota of the parent site, meaning that 10 users used by the child site will consume 10 of the paid user seats purchased by the parent site.

Reselling of child sites is not permitted unless you have a separate reseller agreement with Files.com.

Example Use Case: Departmental Organization

If your company has multiple departments, you could isolate each department into its own child site. This keeps their files, settings, branding, logging, and projects separate from the parent site or other child sites within your company. You can organize the child sites in the same way if your company has multiple subsidiaries.

Example Use Case: Special Projects

Child sites are useful for confidential projects, such as M&A efforts. You can establish a dedicated child site for a project, allowing project teams to customize their setups, including integrations, automations, security settings, and sharing project-specific files.

Example Use Case: Regional Requirements

For companies operating across various geographical locations, child sites can also be used to manage storage or language separately for each region. This facilitates convenient and organized management.

Example Use Case: Development / Staging Environments

A child site offers an ideal way to create staging (sandbox) sites. By utilizing child sites as staging sites, you have a controlled environment to experiment with various changes and updates before implementing them on the production, parent site.

Example Use Case: Incompatible Requirements

If one group of users or flows within your site has requirements that are not compatible with another, a child site provides an isolated container for those exceptions. For example, if a handful of outside partners with legacy systems cannot use the most secure, modern ciphers, those users could connect to a child site set aside for them that allows insecure ciphers, while all of your other users connect to your parent site that requires secure ciphers only.

Similarly, you might need a different maximum number of days for Share Links to be available to separate groups of users. By splitting one group into its own child site, you can change that child site's global Share Link Expiration setting.

Example Use Case: Warm Storage, Archive or Data Retention

Child sites can also be used as a robust solution for businesses and organizations who want to extend their Files.com site as a secure storage archive to meet data retention compliance or regulatory requirements.

By enabling Archive-only mode, files and folders are safeguarded against any unintended modifications or deletions, offering a level of stability and security crucial for compliance-driven environments.