Role management is not possible

[johannesmoormann]

Part 1: Define the problem

What problem are you trying to solve?

During the Great Filter meeting, we agreed on increasing the scope of the problem from a lack of transaction delegate functionality (tx drafter) to the lack of general role management within the interface. Currently, I can only add/remove/replace owners but have no option to determine roles in a more granular way.

What is your hypothesis?

Role management in the interface could enable organizations (DAOs, companies, funds etc.) to define the access logic according to their internal structure and utilize them without requiring development resources (custom modules) which would lead to more Safe creations and stored assets.

What value does this bring to our customers and/or our mission? What is the goal?

Positioning the Safe as a viable decentralized alternative for custodial solutions that fulfill the requirements of role separation for professional safe users (organizations) on an interface level.

Web strategic goal: Default web/desktop interface

How do we measure it?

How is the transaction service delegate feature being used?:
No. of tx delegates
No. of txs proposed by delegates

Links:

Working document see https://www.notion.so/gnosis-safe/Role-Management-894a91099a43479582c53d45277a144e
Kick-off results see https://www.notion.so/gnosis-safe/18-05-Kickoff-fe9a134610cc406398af59a6c5856865

Part 2: Shaping the problem

Problem Owner

@DiogoSoaress
@johannesmoormann

Non Goal(s)

Solution

Solution 1

Part 1: User research on most important roles.
Part 2: Technical research on how to best enable the ecosystem to develop new roles (using the identified key roles as examples), role curation by the ecosystem and enabling the ecosystem to make new roles available in our and other interfaces.

Solution 2

Transaction delegates or transaction drafter role

Exposing the existing transaction delegate feature of the backend in the web application. This mainly includes managing transaction delegates for owners and exposing all transaction proposing capabilities for set transaction delegates.

PoC see 5afe/safe-react#3917

Alternative solutions & ideas

Open Questions

[rmeissner]

but we do not enable this functionality in the interface.

Are we only talking about adding and removing delegates? Are there use cases how users could use delegates in the web interface?

Also in any case exposing delegates in the web interface will require infrastructure support, so the label for this should probably be added.

[tschubotz]

What problem are you trying to solve?

The tx service already allows adding/removing of tx delegates that can propose txs for a Safe but we do not enable this functionality in the interface.

I'd reformulate this a bit so the problem becomes more apparent:

• Delegates can be set, however we don't display that in the interface which is some hidden unexpected functionality, which might be a problem.
• (I assume) There are users that would like to set/remiove delegates in the interface and they currently cannot do that. If so, do we know who they are and how many delegates currently are set?

How do we measure it?

No. of tx delegates
No. of txs proposed by delegates

What are the current numbers for this? Do we know?

[johannesmoormann]

Updated the problem description to provide more clarity.

@tschubotz we were not able to retrieve this data easily at a first look but want to provide more evidence during the shaping phase.

[johannesmoormann]

Initially this issue was only referencing the following problem:

What problem are you trying to solve?

The transaction service already allows adding/removing of tx delegates that can propose txs for a Safe but we do not enable this functionality in the interface.

Management of tx delegates is not supported within the interface (GET/POST/DELETE).
Proposing of transactions as a set delegate is not supported within the interface.

What is your hypothesis?

If we enable the tx delegate feature in the interface, the feature will receive much higher visibility and usability and will increase the number of tx delegates as well as the number of proposed txs by tx delegates.

What value does this bring to our customer and/or our mission? What is the goal?

Necessary functionally for professional Safe users such as teams and DAOs with the need for role separation.

Web strategic goal: Default web/desktop interface