Skip to main content

Creating a Workspace

Only Site Administrators can create Workspaces. When a Site Administrator creates a Workspace, the Workspace gets its own root folder automatically.

Workspaces can be created through the Web App. They can also be provisioned automatically as part of onboarding workflows or infrastructure-as-code practices through the API/SDKs, CLI, and Terraform.

The Default Workspace

Every Files.com site has a Default Workspace, which is the main site itself. Sites that don't use additional Workspaces run entirely within the Default Workspace. All resources (files, folders, users, groups, partners, automations, remote servers, syncs) live in the Default Workspace until additional Workspaces are created.

A New Workspace Starts Fresh

When a Site Administrator creates a new Workspace, it starts as a clean slate. No files, folders, users, groups, partners, automations, syncs, or Remote Servers carry over from the main site. The Workspace Administrator builds out the environment from scratch, creating the folder structure, onboarding users and partners, and configuring automations and integrations for their team, department, or business unit.

Creating a new Workspace does not move or remove any existing resources from the main site. All existing files, folders, users, groups, partners, automations, and integrations on the main site remain unchanged.

If a storage region is configured on the Default Workspace's root folder, the new Workspace receives its own copy of that setting. The setting is managed independently after creation, so changing the Default Workspace's root folder region later does not update existing Workspaces.

Designating Workspace Administrators

After creating a Workspace, the Site Administrator designates one or more Workspace Administrators to manage it. The Site Administrator can:

  • Create a new user for the Workspace and give them Workspace Administrator access. This is common when onboarding a new business unit, department, or team onto the Files.com site.
  • Grant a Default Workspace user Admin permission on the new Workspace's root folder. The user keeps their existing account and can administer more than one Workspace through separate grants.
  • Grant a Default Workspace Group that same root Admin permission. Every member inherits Workspace Administrator access, so an existing team can administer the Workspace without assigning its members individually.

A user who belongs to a Custom Workspace can be designated as its administrator, but cannot receive access to other Workspaces. Workspace Access and Administration explains assignment to existing Default Workspace users and Groups.

Site Administrators do not need to be designated as Workspace Administrators because they already have full access to all Workspaces.