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

# Disclosure updates

> How notice-only and acceptance-required updates reach existing customers, including grace periods and scope-based restrictions.

When a bank publishes a new version of a disclosure, that version becomes the active version as of its effective date. It's presented in all forward-looking flows: new applications and new user and signer onboarding. The update type governs only how existing customers experience the change.

## Notice-only updates

The update takes effect under the account agreement's change-in-terms provisions, and continued use of the account constitutes acceptance.

The bank is responsible for notifying existing customers through its own channels, such as mail or email. Tesouro makes the new version the active one in all forward-looking flows and keeps the current disclosures available to customers in the widget at any time. No action is required from customers and no access is affected.

## Acceptance-required updates

The update requires affirmative acceptance. This can apply at any scope; the scope determines who must accept and what is restricted if they don't.

1. The bank publishes the new version and sets a grace period. The period is bank-configurable, and the default is 90 days.
2. Required acceptors are notified, and the deliveries are recorded.
3. During the grace period, required acceptors are presented the disclosure at login and can defer it. Other users see a banner naming the deadline, and reminders are sent as it approaches.
4. If the requirement is still unmet when the grace period ends, access is restricted at the level matching the disclosure's scope. Read access is always preserved.

A required acceptor can accept at any time, including while restricted. Acceptance lifts the restriction immediately, with no support contact needed.

### Restrictions follow scope

| Unmet requirement | Restriction | Cured when |
| - | - | - |
| `entity` | The account enters a read-only state with no money movement. The restriction applies account-wide because the obligation belongs to the entity. | Any one current Authorized Signer accepts |
| `signer` | Only that signer's signer-capacity actions are restricted | That signer accepts |
| `person` | Only that individual's access is restricted. One user's unaccepted consent never affects the account or other users. | That user accepts |

> [!NOTE]
>
> Acceptance is never forced as a login wall. During and after the grace period, an Authorized Signer can always continue to a read-only view instead of accepting. The business keeps visibility of its funds and the right to decline new terms and wind down. The pressure to accept comes from the restriction itself, not from withholding access to the screen.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.