Why this change?
We introduced the new model to provide a simpler and more flexible way to organize and manage your attack surface.
The previous structure made it difficult to clearly separate responsibilities and control access at a granular level.
With the new Teams model, organizations can structure their environment in a way that better reflects how users actually work, while keeping full control over visibility and permissions.
This change was designed to:
Make the platform easier to understand and configure
Provide clearer separation between different parts of your attack surface
Allow more precise permission management at the object level (Asset, Asset groups, Campaigns) as well as from the Organization administration space
Simplify attack surface management for medium-size and large organizations
Overall, the goal is to give administrators more control while making day-to-day usage more intuitive for all users.
Key concepts
The new model introduces the notion of Teams, which allows an Organization to divide its content into separate working areas.
Each Team can be granted access to specific objects, including Assets, Asset groups, and Campaigns, making it possible to control exactly who can see and manage each part of the attack surface.
Key principles of the new model:
An Organization can be divided into multiple Teams to separate access to Assets, Asset groups, and Campaigns between different groups of users
Users who are not assigned to any Team will not see any content, except for Organization admins who always have full visibility by default
Permissions can now be adjusted directly from the detail page of an object (Asset, Asset group, or Campaign), making access management faster and more explicit
All users, regardless of their role, can see which Teams have access to a given object, ensuring better transparency across the Organization
This approach provides a clearer and more predictable permission model, especially when working with multiple teams or large environments.
What changed compared to the previous model?
The new system removes the previous hierarchical structure and replaces it with a flat model based on Teams.
This means:
There are no longer multiple nested levels — all Teams exist at the same level
Access management is now centered around groups of users rather than structural layers
User workflows are more intuitive, as permissions are managed directly where the objects exist
Because this change impacts how access and visibility are handled across the platform, the feature cannot be enabled independently.
Our team will assist you during the activation process to ensure a smooth transition and proper configuration.