# GitHub settings

GitHub is configured from the shared Capable settings surfaces rather than a tab of its own in every case. This is the complete list.

---

## Every setting

| **Setting**                        | **What it does**                                                                                                                                                                                                             |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| There is no GitHub settings screen | The git capability declares no global settings tab and no space settings tab, so GitHub contributes nothing to Capable global settings or space settings. There is also no admin "connect the site to GitHub" screen, becaus |
| Hide GitHub across the whole site  | Hides the capability tenant-wide. IMPORTANT: this gates the BYLINE ONLY. The macro module has no display conditions, so hiding the capability does not stop existing GitHub macros from rendering on pages.                  |
| Turn GitHub on or off per space    | AlwaysOff suppresses the byline in that space; alwaysOn shows it even on pages with no GitHub macro. Again, byline only. Macros still render.                                                                                |
| Edition and feature flags          | GitHub is edition 'standard', so it is included in both Standard and Advanced, and it sits behind no feature flag.                                                                                                           |
| Unlicensed and anonymous access    | Granted on the MACRO module only, for both 'unlicensed' and 'anonymous'. So a reader outside the licence, or logged out entirely, still sees public file content in the degraded read-only branch.                           |
| Byline visibility conditions       | The byline requires the reader to be logged in with VIEW permission, and then one of: the space-level alwaysOn flag, an existing git content property, or the macro key present in the page's Capable content indexing macro |

---

## A few things worth knowing

* Settings changes can take a minute to reach other people.
* Hiding a capability removes it from the navigation; macros already on pages keep rendering.
* Some settings are per space and need only a space administrator.

---

## Related

[ReferenceLimits and gaps.](https://help.gocapable.com/git/reference.html)

[Capable for ConfluenceSuite-level settings.](https://staging.dev.capable-sites.com/wiki/pages/1412890864)

---

_The complete list, in one table._