Full control of fraud prevention: retuning, disabling and resetting rules, and setting the account's score thresholds. Applies to the same resources as FraudViewerRole so it can be granted on its own without also granting the viewer role, but carries write access as well. This is a consequential role: whoever holds it can raise the block threshold until nothing is refused, or lower it until legitimate customers are, so it belongs with the people accountable for that trade-off rather than with everyone who needs to look at a blocked order.

Implements: Role

---

Properties

---

Inherited from Role

Methods

canConnectToOrganisation()

Returns: boolean

Convenience method for callers, such as Velocity templates, which just need to know if this role can be assigned within an organisation context, without dealing with the TargetType enum directly.

canConnectToRepository()

Returns: boolean

Convenience method for callers, such as Velocity templates, which just need to know if this role can be assigned within a repository (or website) context, without dealing with the TargetType enum directly.

---

Methods

getName()

Returns: String

This role's registered name, "FraudManager".

getPriviledges(CommonResource resource, Repository applicableRepo, Group g)

Returns: Set<Priviledge>

Never reached: this role does not apply to repository-scoped grants. Returns nothing rather than a privilege, so that a future caller cannot accidentally read a grant out of it.

getDescription()

Returns: String

A short, human-readable summary of what this role grants, shown in the role picker.

getCategory()

Returns: String

The group this role is listed under in the role picker.

canConnectTo(TargetType type)

Returns: boolean

Organisation only. Offering a repository-scoped grant would put a control in the group editor that silently does nothing, because the repository-scoped appliesTo overload never matches.