Change limits by policy

A file works when someone already calculated the limits. A policy is for when you want the platform to calculate them: it is a workflow published in the Workflow Builder, in the recommendations category, that looks at a customer and proposes a limit. Running it over a segment gives you one recommendation per customer, grouped in a batch you review before anything changes.

Use a policy when the rule is the same for everyone and depends on each customer's data, such as their payment behavior, their risk rating or their recent activity. Use a file when the numbers come from somewhere else, or when each line needs a value nobody can derive from the data.

Running a policy over a segment

1. Open Modify Limits › Apply policy.
2. In Select a policy, choose the policy. Only active policies of the recommendations category are listed; if there are none, the list says No active policies available.
3. On the Define with segmentation card, click Begin.
4. In Define scope, choose the filters that describe the customers. Scope preview shows how many lines match, their total exposure and their average limit, and updates as you change the filters.
5. Click Apply policy.

The policy then runs once for each matching customer. The screen tells you how many it started, for example Policy applied to 120 customers. Recommendations will update shortly. If some runs could not start, it says how many failed; if none could start, it shows the reason from the first failure, which usually means the policy expects an input it does not receive.

The results arrive as a single batch named after the policy, in the Recommendations tab. From there you review it and apply it like any other batch. A recommendation policy proposes limits: running it changes no limit unless the policy itself is built to write one.

A policy run needs at least one filter, so it cannot be launched over the whole portfolio by accident, and it is limited to 1,000 customers per run. For a larger group, split it into several segments.

Choosing the scope

The Define scope step offers filters from two sources:

• Customer categories, such as the segment a customer belongs to. They are marked with a Category badge. Categories are managed under Customers › Categories.
• Segmentation fields, customer data fields that your organization marked for segmentation and that have a fixed list of values. They are enabled under Settings › Data Models.

Values within one filter are combined with OR, and different filters with AND. Choosing Premium and Gold in the segment filter, plus North in the region filter, selects Premium or Gold customers who are also in the North region.

If the step shows no filters, your organization has not configured any category or segmentation field yet, and the screen tells you where to create one.

Categories can be used for things other than customers, so the list may include one that has nothing to do with them. Choosing it simply matches no lines.

Without a policy: adjusting a segment by a percentage

The same scope step is also available without a policy. In Modify Limits › Manual adjustment, the Define with segmentation card lets you raise or lower every line in a segment by the same percentage. The flow has three steps:

1. Scope: the filters, exactly as above.
2. Configuration: the Change rule (Increase by % or Decrease by %), the Value of the percentage, which applies to each line's current limit, and the same Guardrails as the file upload.
3. Execute: a Label, a Reason for change, and a summary of the impact before and after. As with a file, Apply changes immediately decides whether the button says Create recommendation or Confirm and apply.

This path only touches enabled lines. If you continue without choosing any filter, the scope is every enabled line of your organization, so check Lines found before you continue.

A percentage adjustment has no validity dates. For a change that should revert on its own, use a file. See Temporary changes.

When the file option appears under Apply policy

After choosing a policy, the screen also shows an Upload file with changes card. That option leads to the same upload described in Change limits by file: the limits come from your file, not from the policy.