WES custom hosting

Team settings and templates

Where to find it

  1. In the main sidebar, click Settings.
  2. The page has four sections: Team Deployments, Team Settings, Excluded URLs, and Webflow Webhook.

Only team admins see Settings in the main sidebar. See Members, roles and sign-in.

How team defaults reach your projects

Team settings reach projects in one of three ways. Knowing which one applies tells you what changes when you edit a team value later.

  • Live until a project sets its own value: Publishing mode, Allow Code Component, and Use full asset path. A project follows the team value until someone changes that setting on the project. From then on the project keeps its own value, and later team changes do not affect it.
  • Copied once when a project is created: Root directory and Staging visibility. A new project starts with the team value. Changing the team value later does not change projects that already exist.
  • Applied to every project: Include meta.json. Each time you click Save in Team Settings, WCH applies the Include meta.json value to every project in the team, existing and new.

Team Settings

Change the fields you need, then click Save at the top of the Team Settings section. Nothing in this section is saved until you do.

Root directory

The subfolder your site is placed in inside the archive and the deployed output. New projects start with this value. Leave it empty to place files at the top level. See File Prefix and Root directory.

Staging visibility

Who can open a new project's staging site:

  • Public staging: anyone with the link.
  • Private staging: only people signed in to WCH.
  • Off: no staging site.

New projects start with this value. See Staging site.

Include meta.json

When turned on, WCH adds a meta.json file to the build it deploys to AWS S3, Aliyun OSS, and SFTP destinations. The file records the project, the Webflow site, when and by whom it was published, the destination, and whether caching was on. It sits at the top of the build, or inside the Root directory when one is set.

This setting has no project-level switch. Saving Team Settings applies it to every project in the team.

Use full asset path

Stores downloaded files under the folder path of their original URL inside /files/ and /videos/, instead of in one flat folder. Webflow's main site stylesheets always stay at the top of /files/. Projects follow this value until they set their own. See File Prefix and Root directory.

Allow Code Component

Turns Webflow Code Components on for projects in the team. On a project, the matching switch is Include Code Components. Projects follow the team value until someone changes that switch. See Code Components.

Publishing mode

The default way WCH finds your pages: Sitemap, API, or Url Rewrite. Projects follow this value until someone changes Publishing mode on the project and saves.

Choosing API asks you to connect your Webflow account first. Click Connect and approve access in the Webflow window. Click Cancel to keep the previous mode. See Publishing modes.

Team templates

A team template is a saved AWS S3 or Azure Blob Storage destination. When you add a destination to a project, you can pick a template instead of entering the details again. Templates are useful when many projects deploy to the same bucket or container.

Adding a template

  1. In the Team Deployments section, click Add Deployment.
  2. Choose a Deployment Type: AWS S3 or Azure Blob Storage.
  3. Fill in the form. The fields match the project destination form. See AWS S3 Authentication or Azure: Basic Implementation.
  4. Tick Use project name if several projects will share this bucket or container. See the next section.
  5. Turn on Is Production? if projects should treat this as their live destination. The team can have one production template of each type.
  6. Click Save.

Templates are listed under the AWS S3 and Azure Blob folders in Team Deployments. Click a folder to expand it. Click Update Configuration to edit a template, or Delete to remove it.

Use project name

The name of the zip WCH uploads depends on this checkbox.

  • Ticked: each project uploads a zip named after its Project Alias, for example marketing-site.zip.
  • Not ticked: every project uploads project.zip.

Tick Use project name when projects share a bucket. Without it, every project that uses the template uploads project.zip to the same place, and each publish overwrites the previous project's zip.

Using a template in a project

  1. Open the project and go to Extensions, then Deployments, and click + Add Deployment.
  2. Choose AWS S3 or Azure Blob Storage.
  3. In Use Team Template, pick the template. Templates are listed by bucket and region for AWS S3, and by storage account and container for Azure.
  4. Click Save.

WCH copies the template into the project as a new destination. The copy stands on its own. Editing or deleting the template later does not change destinations that were already created from it. To pick up a template change, delete the project's destination and add it again from the template.

Excluded URLs

URLs you add here apply to every project in the team, on top of each project's own list. Changes apply from the next publish. See Excluded URLs for how matching works.

Webflow Webhook

The Webflow Webhook section sets a default webhook for new destinations. Turn on the toggle, choose a Trigger and a Destination, and click Save. Turning the toggle off removes the default.

With the default in place, adding an AWS S3 or Azure destination to a project shows a Save and create webhook button. It creates the destination and a Webflow webhook bound to it in one step. Click Save instead to create the destination alone. See Webhooks.

Testing your changes

  1. Change a team setting and click Save.
  2. Open a project and check the matching field in its Settings. Projects that set their own value keep it.
  3. For Root directory or Staging visibility, create a new project to see the new default.
  4. Publish one project to staging and confirm the output looks right before you promote.