41 lines
3.8 KiB
Markdown
41 lines
3.8 KiB
Markdown
---
|
|
title: Changing the visibility of your GitHub Pages site
|
|
intro: You can manage access control for your project site by publishing the site publicly or privately.
|
|
product: '{% data reusables.gated-features.private-pages %}'
|
|
versions:
|
|
fpt: '*'
|
|
permissions: 'People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site.'
|
|
redirect_from:
|
|
- /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site
|
|
shortTitle: Change visibility of site
|
|
---
|
|
|
|
## About access control for {% data variables.product.prodname_pages %} sites
|
|
|
|
If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-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 private page to ensure that other repositories in your organization cannot publish content on the same origin as the private page. This protects your private page from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". 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 "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator.
|
|
|
|
To use a shorter and more memorable domain for your private {% data variables.product.prodname_pages %} site, you can configure a custom domain. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site)."
|
|
|
|
## 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 %}
|
|
3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility.
|
|
|
|
4. To see your published site, under "{% data variables.product.prodname_pages %}", click your site's URL.
|
|
|
|
|
|
{% note %}
|
|
|
|
{% data reusables.pages.twenty-minutes-to-publish %}
|
|
|
|
{% endnote %}
|