# Multiple GitHub accounts per person One person can link several GitHub accounts (for example work and personal). Repositories from all connected accounts are merged and de-duplicated in the picker, and when a file cannot be read with one account the macro automatically retries the others. --- ## Where you do it ![The Browse Git Repositories dialog with a Manage Git Connections panel open, showing GitHub with one account connected, an account row with a Disconnect link, and an Add Account button.](https://help.gocapable.com/images/3b83e904-5406-49ed-b3ce-e49d370f96d2.webp) The connection manager lists each account already linked and offers Add Account for the next one. | **Task** | **Where** | | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Connect your GitHub account | On a Confluence page: insert the "Github file (Capable)" macro, then press Connect GitHub in the macro; or open the macro's configuration and press Connect in the Browse GitHub modal. | | Add a file from a repository to a page | Macro configuration → Browse GitHub modal | | Add a file without opening the picker | The Confluence editor | --- ## Settings that affect this | **Setting** | **Where** | **What it does** | | ---------------------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | There is no GitHub settings screen | Nowhere | 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 | App property \`capable-global-hidden-capabilities\`, object name \`hiddenCapabilities\`, value | 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 | Space property \`\_capable\`, object name \`capabilities.alwaysOff\` / \`capabilities. | AlwaysOff suppresses the byline in that space; alwaysOn shows it even on pages with no GitHub macro. Again, byline only. Macros still render. | --- ## Related [Migration from third-party GitHub macrosAnother part of how this works.](https://staging.dev.capable-sites.com/wiki/pages/1417708456) [In-product help catalogAnother part of how this works.](https://help.gocapable.com/git/in-product-help-catalog.html) [How it worksThe rest.](https://help.gocapable.com/git/how-it-works.html) --- _How it actually behaves._