> ## 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 scopes

> Scope answers two questions: who must respond to a disclosure, and what does their response bind?

| Scope | Who responds | What it binds | Satisfied when | Examples |
| - | - | - | - | - |
| `entity` | Any one current Authorized Signer, on behalf of the business | The business entity | Any one current Authorized Signer accepts. The first acceptance clears it for everyone. | Deposit account agreement, fee schedule, funds availability policy |
| `signer` | Each Authorized Signer, in their signing capacity | That signer personally, as to actions on the account | Each Authorized Signer responds individually | Certification of authority, acknowledgment of the current account agreement at signer designation |
| `person` | Every user, for themselves | That individual only, never inherited from another user | Each user responds individually | E-SIGN consent, platform access terms, privacy notice delivery |

## One document, two scopes

A single document can serve two scopes. The deposit agreement is executed once at the entity level when the account opens. Each additional signer later acknowledges it at the signer level. That acknowledgment binds the new signer to terms already in force; it doesn't re-execute the contract.

## Next steps

See [when disclosures are presented](https://docs.tesouro.com/embedded-banking/guides/disclosures/when-presented.md) for which scopes apply at each moment in the customer lifecycle.


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