Conflicts

Upon conducting a Rule check, whether initiated by a campaign or through a manual Rule Check, if the system identifies that an account possesses two conflicting duties prohibited by a rule, a new conflict is generated.

The Conflicts tab, as indicated by the arrow below, is the repository where all conflicts are stored.

the Conflicts tab is marked with an arrow

On the Conflicts list page, you can observe a conflict along with its status, linked application, account, security level, and verification date.

To access more details about a specific conflict, click on the 'View Conflict' button, marked with an arrow below, to open the conflict's window.

on the Conflict List tab, the View Conflict button is marked with an arrow

Within the Conflict window, you can scrutinize its details and opt to either deny or allow the conflict.

the View Conflict window

Allowing a conflict necessitates specifying the resolution and reason, along with selecting a date ("allow until").

This action effectively adds an exception to the rule for the designated period. When the specified time arrives, the conflict will be reevaluated for another review.

This approach is employed when there is no immediate alternative to resolving a permission conflict.

the Allow Conflict form

An allowed conflict is designated as "Allowed," as circled below. Additionally, marked with an arrow below is the 'Exception Added' button, which facilitates the viewing of the reason and 'Allow Till' date associated with the approved conflict.

an allowed conflict, the 'Exception Added' button is marked with an arrow

By opting to deny a conflict, we designate a collaborator to rectify it.

The collaborator will receive a conflict notification, eliminate one of the user's duties or roles, and subsequently mark it as fixed.

the Deny window - sending notification to a Collaborator

To return to the Access Management Guide hub, click here.

To return to the main guide hub, click here.