You have a static site in a GitHub repository. Someone who is not a developer keeps asking you to change the words on it. This removes you from that loop without giving them your credentials.
1. Connect GitHub once
Add a classic personal access token in the admin. It is encrypted and stored on the server. Nobody you invite ever sees it, and it is never sent to a browser.
2. Grant access, repository by repository
Access is assigned per person, per repository. One colleague might reach two repositories; another reaches a different three. Change or revoke it whenever you like. Private repositories work exactly the same way.
This is the part GitHub itself makes awkward. Adding someone as a collaborator usually hands over far more than the job needs.
3. They make the change
There are three ways in, and they all reach the same repositories with the same permissions:
- The admin panel — browse the repository, open a file, edit it, commit. Nothing to install.
- Claude Desktop — install the extension and talk to your repositories in plain language.
- A custom GPT — connect ChatGPT to your account and do the same from there.
Whichever they use, the result is an ordinary commit in your repository. Your existing GitHub Action picks it up and deploys, whether that is GitHub Pages or Azure Static Web Apps.
What this is for, and what it is not
It suits static sites — React, Next.js, plain HTML, anything that builds from files in a repository. Content and copy changes are where it earns its keep.
It is not for applications with a database, and it does not manage servers or environments. If your change means a schema migration, this is the wrong tool.