Why can't I delete a target?

Why this happens

Each action in Cyberlop checks one permission. Reading a target needs target:read. Creating one needs target:create. Removing one needs target:delete, and a custom role can hold the first two without the third.

How to fix it

1. Open Targets and find the row. The delete icon sits in the Actions column.
2. Missing icon, or a refused click? Your role lacks target:delete.
3. Before anyone deletes, use Export JSON or Export CSV on Targets, and the export buttons on Issues, to keep a copy of what you need.
4. Ask an admin to add the key to your role, or to delete the target for you. Read which permissions a custom role can hold if you want to name the key exactly.
5. Click the delete icon again once the role changes.

Think hard before you confirm. The delete also removes the target's profiles, schedules, scans and findings, and you cannot undo it. Targets are also fixed after creation, so the only way to change a Main URL or repository is to delete the target and create it again.

Still not working?

• Only want to clear old runs? Deleting a scan needs scan:delete, and it keeps the target's findings.
• Cannot see the target at all? A group may limit your access. Read why some targets are missing.

Still blocked after the role change? Send us the target name and your role on the contact page.

Related questions

• How do I delete a target?
• Why can't I see some targets that my colleague can see?
• I deleted a target and its profiles, schedules, scans and findings disappeared too. Why?
• Which permissions can I give a custom role?
• I deleted a scan, but its findings are still on the Issues page. Why?

Full tutorial

How to manage targets in Cyberlop: list, export, change and delete

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre