Your agency has asked for access to GitHub. You don't need to share your password for it. GitHub lets you add them with their own login, choose exactly what they can do, and remove them when the project ends. These are the clicks, checked against GitHub's own help pages in October 2026.
Which role to choose
Pick the narrowest role that lets your agency do the work. Write is usually the right one.
| Role | What it allows | For an agency |
|---|---|---|
| Write | Pushes code and manages issues and pull requests. You keep ownership. | Usually the right one |
| Maintain | Write, plus repository settings that do not touch security or deletion. | If the work needs it |
| Admin | Full control of the repository, including deleting it. | If the work needs it |
Add your agency to GitHub
- Open your repository on GitHub and click Settings.
- Click Collaborators and teams (Collaborators on a personal account), then Add people.
- Enter your agency's GitHub username, choose Write and click Add.
How you both know it worked
GitHub emails your agency an invitation from github.com. Once they accept it, they show in your GitHub account's list of people with access, where you can see or change their role at any time.
Remove access when the project ends
- Open your repository settings, then Collaborators and teams.
- Remove your agency's account.
- Remove any deploy keys or tokens your agency added.
Do you have to share your password?
No. Every step above uses GitHub's own invite, so your agency signs in with their own account, your two-step verification stays on, and anything they change is recorded under their name. How to give a developer access without sharing your password covers the other accounts agencies usually ask for.
Doing this for every client?
Agencies can send each client one Get Set Keys link instead of a page like this. It walks the client through GitHub and the other platforms the project needs, and checks that each step is done.