Why can't I see some targets that my colleague can see?

Why this happens

The Security page says Cyberlop uses role-based permissions, with grants scoped to groups of targets. A role says what you may do. A grant says on which targets. If your grant covers fewer targets than your colleague’s, your list is shorter by design.

How to fix it

1. Look at the role badge in the header next to your email. Built-in roles include SuperAdmin and Developer, and admins can create custom roles.
2. Clear any text in the search box on Targets. A search can hide rows.
3. Ask what role they hold. Different roles carry different permissions, such as target:read.
4. An admin can see each user’s role and team grants in Administration and adjust them.
5. After the change, reload Targets and the target picker.

The same scope applies to API tokens. A token carries its owner’s permissions and group scope, so a script can see exactly the targets its owner can see. This keeps one team’s targets away from another team.

Still not working?

Only an admin can change access, and the Administration screens were not part of the public capture, so this guide cannot show them step by step. Read how to limit access to profiles, how to see roles and grants and what groups are for. If you are an admin and the list still looks wrong, reach us through the contact page.

Related questions

• Can I give someone access to only some of our targets?
• How do I see each user's role and team grants?
• How can I see which role I'm signed in with?
• What are groups used for?
• Which roles come built in?

Full tutorial

How to group scan profiles by tag and group in Cyberlop

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre