Skip to main content

Managing permissions with Teams

H
Written by Hervieu
Updated this week

How it works

With the new model, Organizations can now be structured using Teams, which represent groups of users with specific access rights.

Each Team can be granted access to selected objects, allowing administrators to control exactly which users can see and manage different parts of the attack surface.

The main principles are the following:

  • An Organization can be divided into multiple Teams, each representing a group of users

  • Organization admins can grant, update, or remove access permissions at any time

  • Users assigned to one or more Teams can only see the content their Teams have access to

  • A user can belong to multiple Teams at the same time, and their visibility will be the combination of all assigned permissions

This model makes it easier to manage large environments while keeping access control precise and predictable.


User roles and permissions

Access to permission management depends on the user role within the Organization.

  • Standard users can view which Teams have access to an object, but cannot modify permissions

  • Auditor users can also view permissions, but cannot make changes

  • Organization admins are the only users who can view, create, modify, and remove permissions

This ensures that access control remains centralized while still allowing full transparency for all users.


Access to Assets

Teams can be granted access to individual Assets, allowing users to see and interact only with the objects they are authorized to access.

  • A Team can be given access to one or multiple Assets

  • Permissions defined at the Asset level can be managed directly from the Asset detail page

  • If access to an Asset is inherited from an Asset group or a Campaign, the permission cannot be removed from the Asset itself

In this case, the permission must be modified at the level where it was originally granted.


Access to Asset groups

Teams can also be granted access to Asset groups, which allows permissions to be applied to multiple Assets at once.

  • A Team can be given access to one or multiple Asset groups

  • When a Team has access to an Asset group, it automatically has access to all Assets included in that group

This makes it easier to manage permissions when working with large numbers of Assets.


Access to Campaigns

Permissions can also be assigned at the Campaign level.

  • A Team can be granted access to one or multiple Campaigns

  • When a Team has access to a Campaign, it can see all Assets included in that Campaign

  • The Team will also have visibility on the vulnerabilities associated with those Assets

Managing access at the Campaign level is recommended when permissions need to follow the scope of an assessment or a specific project.

Did this answer your question?