Rules can be applied at different levels of the system hierarchy, each representing a broader or narrower scope of effect. Importantly, rule scopes are inherited downward - a rule set at a higher level will automatically apply to all levels beneath it, unless explicitly waived.

The hierarchy of scopes, from broadest to most specific, is as follows:

Client

All cards under this client will be evaluated for the rule applied at this scope.

Sub-Client

All cards under this sub-client will be evaluated for the rule applied at this scope.

Product

All cards under this product will be evaluated for the rule applied at this scope.

Parent Account

All cards who's main account is a child of this parent account will be evaluated for the rule applied at this scope.

Account

All cards who's main account is that of this account, will be evaluated for the rule applied at this scope.

Card Group

All cards who belong to this group will be evaluated for the rule applied at this scope

flowchart TD
    C["Client"] --> SC["Sub-Client"]

    SC --> P["Product"]
    SC --> PA["Parent Account"]
    SC --> G["Groups"]

    G --> AG["Account Group"]
    G --> CG["Card Group"]

    P --> CARD["Cards"]
    PA --> CARD
    AG --> CARD
    CG --> CARD

📘

Understanding this structure is key to effectively targeting rules across different entities.