How do I add my own AI credential for scans I start?

Steps

This is your own setting. You do not need an admin to change it.

STEPS

Good to know

The page says Cyberlop uses tokens set here first for scans you launch, and falls back to the organisation's shared token if you leave yours unset. Scans that other people start do not use your credential.

Cyberlop encrypts the secret at rest and never shows it again after you save, and a shield note on the card says as much. Expect the field to look empty the next time you visit.

Prefer an API key when you can. A subscription token carries rate limits and can be throttled part-way through a scan, so the agents may cover less of the code. Read API key or OAuth token for the trade-off.

Your provider bills usage on your own key, not Cyberlop. Treat the key like a password, and rotate it when you leave a project or change roles.

The organisation also has a shared credential that an admin manages under Settings. To compare the two, read personal and organisation AI credentials. Questions? Ask on the contact page.

A personal credential also helps when you want your own scans billed to your own provider account, or when you wish to try a different provider type without touching what the whole workspace uses. Colleagues who never set one simply keep using the shared credential. That is the point of the fallback.

Related questions

• What's the difference between my personal AI credential and the organization's?
• How do I use my organization's own AI provider key?
• Should I use an API key or a subscription OAuth token for my AI provider?
• Why didn't a teammate's scan use my personal AI credential?
• How do I check that my AI provider credential works?

Full tutorial

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

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre