Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Workspace settings

Workspace settings

If both I and my organization have a token set, which one does a scan use?

Quick answer

Your own token comes first. For scans you launch, Cyberlop uses the Git token or AI credential you saved on My Account. With none set, it falls back to the organisation's shared token from Settings. This applies to your scans only.

The short version

Yours wins. For a scan you launch, Cyberlop looks at your own token first. If you have not set one, it falls back to the organisation's shared token.

How it works in Cyberlop

The My Account page says it plainly. Cyberlop uses the tokens you set there first for scans you launch, and falls back to the organisation's shared token if you left them unset. The rule holds for two kinds of secret.

SecretYour own (My Account)Shared (Settings)
Git token for private repositoriesUsed first for scans you startUsed when you have none
AI provider credentialUsed first for scans you startUsed when you have none

The words "scans you launch" matter. It belongs to you, so it applies to your scans only. A teammate's scan uses their own token if they set one, and the shared one if they did not.

Each token has a status at the right of its card, either "Not set" or a configured state. Cyberlop encrypts secrets and never shows them again after you save, so a blank field does not mean empty. Look at the status instead.

What to do next

Decide who should own the access. A shared token keeps scans running when people leave, while a personal token lets one person use their own access or their own AI billing. Many teams set only the organisation token and keep it read-only.

See personal and organisation Git tokens for the differences. If a scan used the wrong token, read why a scan used the organisation's token and why a teammate's scan did not use your key.

Full tutorial

Account and organisation settings: notifications, retention, logo and plan

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.