Skip to main content
By default, every member of a Gecko team sees every repository the team has connected. Turn on repository access and Gecko mirrors your Git host instead: each member sees the repositories, findings, and scans of the GitHub and GitLab repositories they can push to, and nothing else.
Only team Admins can change repository access.

​
How it works

Each member links their own GitHub or GitLab account to their Gecko user. Gecko then checks, per member, which of the team’s connected repositories that account can push to, and keeps the list in sync. Repository access applies everywhere a member reads data: the dashboard, findings, scans, exports, and their personal API keys and MCP connections. Roles still decide what a member can do; repository access decides what they can see.

​
Turn it on

1

Link your own account first

Go to Settings > General > Personal connections and click Connect next to GitHub or GitLab. Gecko blocks the switch until you have, so you don’t lock yourself out.
2

Enforce Git permissions

Go to Settings > Members. Under Repository access, turn on Enforce GitHub/GitLab permissions and confirm.
3

Check the Access column

The Access column on the Members page shows how many repositories each member can see. Members marked Not linked see nothing until they connect their Git account.
ZIP uploads are turned off while repository access is on.

​
Turn it off

Turn off Enforce GitHub/GitLab permissions in Settings > Members. Every member sees every repository again right away.