Turn classic Sites on or off for users

This article is for administrators of the classic Google Sites (no Publish button at the top right). Get help for administrators of the new Google Sites.

If you have Drive Enterprise edition, classic Sites are not available. You can use new Sites or upgrade to G Suite Enterprise to get classic Sites.

As a G Suite administrator, you can turn classic Sites on or off for people in your organization. People who have classic Sites turned on can use it to create and manage websites at your domain's web address. 

Using multiple domains? People in all your domains can use Sites.

To control who uses classic Sites in your organization

Before you begin: To turn the service on or off for a set of users, put their accounts in an organizational unit.

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenG Suiteand thenSites.
  3. At the top right of the gray box, click Edit Service Compose.

  4. To apply settings to all organizations, click On for everyone or Off for everyone, and then click Save

  5. To apply settings to individual organizational units, do the following: 

    • At the left, select the organizational unit that contains the users whose settings you want to change.
    • To change the setting, select On or Off.
    • To keep the setting the same, even if the parent setting changes, click Override.
    • If the organization's status is already Overridden, choose an option:
      Inherit—Reverts to the same setting as its parent.
      Save—Saves your new setting (even if the parent setting changes).

    Learn more about the organizational structure.

Changes typically take effect in minutes, but can take up to 24 hours. For details, see Admin console settings don't update.  

If you manage a large number of users or sync your LDAP directory

You can use access groups to turn on a service for specific users within an organizational unit. You turn off the service for the organization, and then add the users to an access group that has the service turned on. This lets you give users access to services without making changes to your organizational structure. Learn about access groups.

Impact of turning off classic Sites access

If the class Sites service is turned off:

  • An error message is displayed to users indicating that they don't have access to Sites and should contact their domain administrator to provide access.
  • Users can't access existing Sites, pages, or a list of all sites.
  • The classic Sites API doesn't work.
  • Site project files aren’t deleted, but they can’t be accessed. If Sites is turned back on, people can access their site project files.

Next steps

Was this helpful?
How can we improve it?