# Allowances

## Considerations
- have an ENV variable with the module addresses for the supported networks (Rinkeby, Mainnet, ganache?)
- verify that the expected `address` for the **Allowances** module is enabled (by calling `isModuleEnabled(address)`)
- we can load all the enabled modules at safe's startup, as it will be useful for other functionalities (by calling `getModules()` -not sure about the pagination response: how shall we handle that?-). See: https://github.com/gnosis/safe-react/issues/934
- if module is enabled and there are allowances set, enable app-wide the _allowance_ feature. That is:
- allow to use the allowance to transfer funds. See: https://github.com/gnosis/safe-react/issues/693
- enable the sApp that will interact with the Allowance Module
- if module is not enabled or no allowances set, disable app-wide the _allowance_ feature. That is:
- no allowance option displayed.
- Show intro/explanation screen.

## Questions
- as _allowance_ module status will be required by the Safe-App and by the sApps, shall we replicate the same logic in both codebases? or we can share that information from the Safe-App into the sApp somehow?
- Given that we default to multiSend txs in sApps, will be an option to set a batch of allowances and submit them in one single tx? If so, we should also support batch remove.
- Shall we inform the user that, if the Module was disabled, they first tx will include the `enableModule()` call too?
- Is there any contract for Allowances? If not, can we have a list of methods and they signatures to mock on our side? Or can we just use `DailyLimitModule` as an approximation?

---
So far, work can be divided into two or three teams. One for the presentation/components creation, other on the sApp creation and the last on the Safe-App implementation.