> For the complete documentation index, see [llms.txt](https://sector-finance.gitbook.io/sector-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sector-finance.gitbook.io/sector-finance/sector-dao/permissions-architecture.md).

# Permissions Architecture

Sector is a non-custodial protocol. This means the admins of the Sector smart contracts will never be able to walk away with user funds.

For a protocol like Sector this is a challenge because the team needs to have an ability to add, remove and update investment strategies. To ensure the protocol remains non-custodial, we are putting all critical owner actions like adding strategies or changing configuration parameters behind a Timelock contract with an initial delay of 5 days. This means any owner transactions will first need to be submitted to the Timelock contract and 5 days will need to pass before the transaction can be executed. This gives users 5 days to inspect the pending admin transaction and decide whether it is safe to keep their deposits in the pool.

Diagram of the permissions architecture:

 

<figure><img src="/files/gq15naBIBvtT8eBZVkG8" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/obroKD3i6v1zkBN96BN8" alt=""><figcaption></figcaption></figure>