Overview
This article explains what an engagement is in Hyver, how it’s used, and who can create or manage it. You’ll learn the role engagements play in assessments and how permissions affect who can take action.
If you're new to working with engagements in Hyver, this is the place to start.
What is an engagement?
An engagement is a defined project within Hyver that scopes the assessment to be carried out — either by CYE’s services team or by your organization. It acts as the operational container for risk analysis, findings, and mitigation planning.
Engagements can be created either by customers directly in Hyver, or by CYE personnel. However, before any security assessment begins, the engagement must be activated.
Active vs. inactive engagements
Once activated, an engagement signals that an assessment is underway or about to begin, according to its schedule. From this point, users with the right permissions can begin adding findings to it.
Before activation, all engagement definitions (such as scope and settings) are saved in Hyver — but the actual assessment process has not started yet.
Who can create and activate an engagement?
Administrators or Power Users can create new engagements.
These same users can also activate most engagement types — with a few exceptions.
Asset Discovery, Internet Perimeter, and Cloud assessments are special cases: only the CYE service team can activate them.
Permissions and roles
To contribute findings or build the mitigation graph for an engagement, users need specific permissions:
Editors must have the Findings & Graph Initiator permission.
These users will appear in the engagement as members with the Power User and Initiator role.
Wrap-up / Next Steps
Understanding how engagements work is key to managing your organization’s security assessments in Hyver. Once you’ve got the basics down, you can move on to creating, activating, or editing specific engagements — depending on your needs.
Feel free to skip ahead or take it slow — whatever fits how you like to work.