Repository navigation
Permission Levels for Team Members
Your access to DevOps work comes from two separate systems, and being added to one does not add you to the other:
-
GitHub — which repositories you can read, push to, and merge into. Comes from being in a
devops-*GitHub team. - AWS — what you can see and change in the incubator AWS account. Comes from being in an AWS IAM group.
This page describes both. If you are new, read Joining the DevOps team first — it covers how you get added in the first place; this page covers what you get once you are.
There are five DevOps GitHub teams. They form a ladder, and each one grants across all four DevOps repositories at once — there is no per-repository membership.
| Team | GitHub role | What it lets you do |
|---|---|---|
devops-read |
Read | Be assigned issues, be requested as a reviewer. This is where a new member starts. |
devops-write |
Write | Everything above, plus push branches to the repositories and open pull requests. This is the level most contributors work at. |
devops-merge |
Write | Everything above, plus merge an approved pull request into the default branch. See "What merging actually requires" below. |
devops-maintain |
Maintain | Everything devops-write has, plus repository housekeeping: managing labels, milestones, and settings that are not access control. |
devops-admin |
Admin | Full control, including repository settings, branch protection, and team access. Held by the CoP leads. |
The four repositories all five teams cover:
| Repository | Default branch | What it is |
|---|---|---|
| devops | master |
The Community of Practice itself — meeting agendas, shared GitHub Actions tooling, and this wiki |
| devops-security | main |
AWS IAM as code, in Terraform |
| incubator | main |
The shared AWS infrastructure that project teams deploy onto, in Terraform |
| check-ghpages-versions | main |
The @danielridgebot bot, which watches GitHub Pages versions |
Because a team grants on all four, there is no such thing as having devops-security access but not incubator access. If you can push to one, you can push to all of them.
The organisation also has teams called incubator, incubator-write, incubator-merge, incubator-maintain and incubator-admin. They have nothing to do with the incubator repository. They grant access to project application repositories — VRMS, HomeUniteUs and ballotnav — and grant nothing on any DevOps repository.
The names are misleading, so to be explicit: if you want access to the incubator repository, you need a devops-* team. Being in incubator-admin gives you no DevOps access at all.
Write access lets you push a branch and open a pull request. It does not let you merge into the default branch. All four repositories share the same two rules:
- Pushing directly to the default branch is restricted to the
devops-mergeteam. - A pull request needs one approving review before it can be merged.
In both cases a review approves a particular state of the branch rather than the branch in general, though the repositories get there by slightly different routes: on devops, devops-security and incubator, pushing new commits dismisses existing approvals, while on check-ghpages-versions the most recent push must itself be approved.
So the normal path for anyone at devops-write is: push a branch, open a pull request, get a review, and have someone in devops-merge merge it. Note that devops-maintain does not include merge rights — maintain covers repository housekeeping, not the default branch.
Members of devops-admin are exempt from all of the above, deliberately. Branch protection on these repositories is configured not to apply to administrators, so a CoP lead can push to the default branch and merge without a review. This is an intentional choice rather than an oversight — please do not "fix" it — but it does mean the protections above describe how the team works by agreement, not a rule the platform enforces on everyone.
AWS access is separate from GitHub and is granted by adding your IAM user to a group. This section covers the incubator account only — the account holding the shared infrastructure the projects run on. Access to the Hack for LA organisation (payer) account is handled differently and is out of scope here.
| Group | What it grants |
|---|---|
read-only-group |
Read access across the account, the ability to change your own password, and enforced MFA. The starting point for anyone who needs to look at infrastructure. |
project-leads |
Working access to the services projects actually use — Terraform state, Route 53, Cognito, ECS, DynamoDB, and read access to CloudWatch Logs. |
ops-leads |
Full administrative access to the account, plus access key management. Held by the CoP leads. |
Two things worth knowing:
-
GitHub access does not imply AWS access. Most people in the
devops-*teams have no AWS user at all, and that is normal — you only need one if your work touches the infrastructure directly. - Automation does not use these groups. Terraform runs from GitHub Actions under short-lived roles assumed via OIDC, not under anyone's personal credentials.
Accurate as of 2026-09-07. The AWS group model is being reworked as part of the DevOps CoP's IAM access work — the intended replacement is per-project groups whose permissions follow resource tags, rather than the three broad groups above. Check with a CoP lead before relying on this section for anything consequential.
For emergency access when normal access is unavailable, see the Break-glass Account Guide. That is a separate mechanism from anything on this page and is not something to set up for yourself.
Ask in the #ops Slack channel, or raise it with a DevOps CoP Lead at the weekly CoP meeting. Say what you are trying to do rather than which team you want — the right level usually follows from the work.
Access levels go up as you take on more. Moving from devops-read to devops-write is the normal first step and follows from actually contributing; devops-merge and above are held by people carrying responsibility for the repositories.
Current membership of each team is on the organisation teams page, which is the accurate source — it is deliberately not listed here, because it changes.