> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Usage Limits

> Cap daily and monthly TED transfer volume in Lerian Console — enable Usage Limits to enforce guardrails against runaway automations and risk policies.

The **Usage Limits** section caps how much value each account can move in a given day or month. Use it to enforce operational guardrails — catch configuration mistakes, prevent runaway automations, and comply with internal risk policies.

The section header shows an **Enabled** or **Disabled** badge that matches the toggle below.

## Accessing the section

***

<Steps>
  <Step title="Open Settings">
    In the Bank Transfer sidebar, click **Settings**.
  </Step>

  <Step title="Expand Usage Limits">
    Click the section header to expand it.
  </Step>
</Steps>

## Fields

***

### Limits Enabled

Toggle that turns enforcement on or off. When the toggle is off, the Daily Limit and Monthly Limit fields stay editable but inactive. The plugin applies no cap until you turn the toggle on.

### Daily Limit

The maximum total value of transfers the plugin allows per day. Enter it in regular currency units — for example, `100.00` for R\$ 100.00. The plugin stores the value internally in cents. You can edit this field only when you enable limits.

### Monthly Limit

The maximum total value of transfers the plugin allows per month. It uses the same input format as the Daily Limit. You can edit this field only when you enable limits.

## How limits are applied

***

When you start a transfer, the plugin adds up the account's transfer value for the day and for the month. It compares each total against the configured cap. If the transfer would push either total past its cap, the plugin rejects it before it reaches JD.

<Note>
  Limits apply to the total value of transfers that you initiate through the plugin. The JD poller receives inbound TED transfers (TED In) passively, so they do not count against these caps.
</Note>

## Saving changes

***

Click **Save** in the toolbar at the top of the page. The Console records every change in the [Settings History](/en/rails/ted/console/bt-viewing-settings-history) tab. The plugin stores monetary values in cents internally, and the history reflects that.

## Tips

***

* When you roll out the plugin, start with conservative limits. Raise them gradually as you gain confidence in the flow.
* If a limit blocks a legitimate operation, raise the cap, wait for the save to register in the history, then retry the transfer. You cannot bypass a cap for a single transfer without first adjusting the setting.