Request for new policy conditions: isReviewer() and !isReviewer

[ramonadiaconu]

hi team,

I would like to request the addition of two new functional conditions for policy rules: isReviewer() and !isReviewer. These would enable the creation of policies specifically aimed at reviewers.

At present, the data steward role exists OOTB. However, this also grants stewards the ability to directly edit business glossary terms across all business areas- including those outside their own domains (particularly relevant in organisations where the Domains feature in OPM is not in use).

Having access to isReviewer() and !isReviewer conditions would allow us to design more granular policies that:

• restrict edit permissions appropriately when domain boundaries are not applied.
• support reviewer-specific workflows, such as allowing suggestions to be reviewed by other reviewers rather than by the same individual.

Essentially, the goal is to create a reviewer-focused policy similar in structure to the existing OrganisationPolicy-Owner-Rule, but scoped to owners instead of reviewers.

Would it be possible to include these two conditions in the next update?

Many thanks!