Introduction to on-chain roles

Roles give the appropriate level of access to different contributors and entities. Roles are administrative rights granted to Safe smart accounts, externally owned accounts (EOA), or other smart contracts inside the Palmera Module.

To understand roles better, we need to establish 2 types of basic relationships present within the hierarchical structure: Super Safe smart accounts (parent) and subsafe smart accounts (child). Let's look at the following diagram to better illustrate these ideas.

Root Safe

Root Safe

This is the Safe smart accounts positioned at the top of the hierarchy structure. It can be viewed as the control tower in charge of supervising and controlling the rest of the structure.

It has admin rights over any safe located in all levels below it, additionally it can add or remove EOAs, or smart contracts from its hierarchy structure.

Super Safes and subSafe smart accounts

Super Safe smart accounts (parent)

A super Safe smart account (parent Safe smart account) refers to any Safe smart account that has a subsafe account (child safes account). It can also be defined as any Safe that has rights over another Safe located one level down in the hierarchy structure. This role is useful to limit the amount of control and the kind of operations subsafes can perform.

SubSafes Account (child)

A subsafe account is any Safe smart accounts that has a Super Safe smart account (parent Safe smart account), in other words, a subsafe refers to any Safe that has another Safe smart account located one level up in the hierarchy structure. This role is ideal for granting Safe certain rights while limiting the amount of control they have over the rest of the hierarchical structure.