Home / Help centre / Workspace settings
Workspace settings
Why did my scan use the organization's Git token instead of mine?
Cyberlop uses your personal token first for scans you launch, then falls back to the organisation token. If your token shows Not set, or someone else launched the scan, the organisation token applies. Save your token on My Account and start the scan yourself.
Why this happens
The My Account page sets the order. Your own token comes first for scans you launch, and the organisation’s shared token steps in when yours is unset. Two things follow, and both are easy to check. A personal token must exist, and you must be the person who launches the scan, because the app picks the token from whoever pressed the button.
With a status of Not set, the save did not go through or you never saved one. When a teammate presses Scan, their own tokens apply to that run, then the shared one. That can look as if Cyberlop ignored yours, when in fact it simply used the token of the person who started the run.
How to fix it
- Open My Account and look at the status on the right of the Git access token card.
- If it says Not set, paste the token into the password field. Use a read-only token, since Cyberlop only needs to read your code in order to clone it, and nothing more than that.
- Press Save Git token. The field then looks empty, which is normal because secrets never show again.
- Start the scan yourself from the target or the profile.
- Check the scan on the Recent Scans page for the clone result.
Still not working?
- The token itself must reach the repository. A token with too little access fails to clone a private repo.
- The organisation token only goes to the allowed hosts listed under Settings. See Git allowed hosts.
- Compare both tokens in personal versus organisation Git token.
If the wrong token still seems to win, tell us at /contact.
Related questions
- If both I and my organization have a token set, which one does a scan use?
- How do I add my own personal Git token?
- What's the difference between my personal Git token and the organization's Git token?
- My private repository won't clone. What do I need?
- What permissions should my Git token have?
Git access in Cyberlop: set a read-only token and allowed hosts
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Still stuck?
Tell us what you see on screen and an engineer will help you sort it out.