Access control for GitHub Pages

Hi @berryp - this feature is currently only available for organisations on Enterprise Cloud plan. If you are on that plan, and you still cannot select this option, please open a ticket

1 Like

Is there a plan for what GHE release this will get into? My company uses a hosted (non-cloud) Github Enterprise and I’d like to what release # I’d be waiting for to get this feature.

1 Like

Great addition. When will this come to regular GitHub organizations?

@ggould-tri :wave: I don’t see it in the next rc, but I know folks like you are showing interest so I’d hope it’ll show up soon. To some extent, Enterprise Server customers have been able to do this for a while, if they are running their instance in private mode.

In that case, it’s enabling public pages that becomes the option:

Hi @tomlankhorst - I don’t see this roadmapped right now, but seeing as it has only just been released for one product, that isn’t surprising. You can always check in with our public roadmap to see what is upcoming.

2 Likes

Thanks! My organization mandates internal access control for all of our data, so anything that gets me closer to being able to use the repository ACL for the pages site is all good in my book! I’m looking forward to this.

Is this feature supported with the organizational page at <organization>.github.io? When I create the repo and set it to internal I don’t get the option to set the visibility of the pages site in the repo settings, it defaults to publishing the pages site publicly.

@jrauen That should definitely work on an internal repository in an Enterprise Cloud organisation. If you haven’t already, please open a ticket so we can have a look at the configuration privately and figure out what might be going wrong.

While working this issue with support I discovered this in the documentation:

It specifically says You cannot manage access control for an organization site. So I guess this isn’t supported as of yet. Are there any plans to support this in the future? It’s not a big deal if not since I can just make it into a project repo and then use a custom domain to host it.