docs/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md

title, intro, versions, permissions, redirect_from, shortTitle

title	intro	versions	permissions	redirect_from	shortTitle
Changing the visibility of your GitHub Pages site	You can manage access control for your project site by publishing the site publicly or privately.	ghec *	People with admin access to a repository can change the visibility of a {% data variables.product.prodname_pages %} site.	/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site	Change visibility of site

About access control for {% data variables.product.prodname_pages %} sites

With access control for {% data variables.product.prodname_pages %}, you can restrict access to your project site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise.

{% data reusables.pages.privately-publish-ghec-only %}

If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. For more information about {% data variables.product.prodname_emus %}, see "AUTOTITLE."

If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your project sites privately or publicly to anyone on the internet.

Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "AUTOTITLE."

About subdomains for privately published sites

Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published:

• We automatically secure every subdomain of *.pages.github.io with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS.
• We use a unique subdomain for the privately published site to ensure that other repositories in your organization cannot publish content on the same origin as the site. This protects your site from "cookie tossing". This is also why we don't host {% data variables.product.prodname_pages %} sites on the github.com domain.

You can see your site's unique subdomain in the "Pages" tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "AUTOTITLE" or the documentation for your static site generator.

To use a shorter and more memorable domain for your privately published site, you can configure a custom domain. For more information, see "AUTOTITLE."

Changing the visibility of your {% data variables.product.prodname_pages %} site

{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}

1. Under "{% data variables.product.prodname_pages %}", select the {% data variables.product.prodname_pages %} visibility dropdown menu, then select a visibility.

2. To see your published site, under "{% data variables.product.prodname_pages %}", click {% octicon "link-external" aria-hidden="true" %} Visit site.

   

{% data reusables.pages.twenty-minutes-to-publish %}