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

Why didn't a teammate's scan use my personal AI credential?

Quick answer

Your personal AI credential belongs to you. Cyberlop uses it first for scans you launch, and falls back to the organisation's shared setting if you leave it unset. A scan a teammate starts uses their credential, or the shared one.

Why this happens

The AI provider credential card on My Account is personal. Cyberlop tries what you set there first for scans you launch. It falls back to the organisation's shared credential if left unset.

So the person who starts a scan decides which credential is tried first. Your credential does not follow your name onto a teammate's scan. This also stops one person's key from paying for work that another person started, which is why every teammate sets their own or relies on the shared one.

How to fix it

  1. Open Recent Scans and read the Run by column. Confirm who launched the scan in question.
  2. If you want your key used, launch the scan yourself, or press Scan on the row to re-run the same profile as you.
  3. If the whole team should use one key, ask an admin to set the shared credential in Settings. Scans then fall back to it whenever someone has no personal one.
  4. Ask your teammate to open My Account and add their own credential under AI provider credential, then press Save AI credential.

Cyberlop encrypts secrets at rest and never shows them again after saving, so you cannot read a saved key back. To change one, save a new value.

Still not working?

  • Look at the status beside the card. It reads Not set until a credential is saved.
  • Check whether the scan was started by schedule or from CI. Those runs are not launched by you at the keyboard.
  • Make sure the Provider you picked matches the type of secret you pasted, since a mismatch is a common reason a saved credential does not behave as you expect.

Still stuck? Contact us with the scan link. For the two options side by side, see personal and organisation AI credentials and the AI provider settings tutorial.

Full tutorial

AI provider settings: included allowance, your own credential and models

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.