Feature Requests for better usability in teams

[gitpusha]

Hi everyone,

I am a heavy GnosisSafe user. Everytime I am using the web UI I think off some feature requests I have but I never know where to best submit them. So I decided to open this issue and share it on discord. I apologize if not all of the requests in here are fitting for this repo. Some of them might be more on the Safe modules or frontend side of things, but here goes anyway:

• [ ] Different types of owners and policies: super-owners vs. owners ( smart contract )

It would be useful to have e.g. a super-owner and an owner type. In a multisig of 5 with 3 owners and 2 super-owners the policy could then be 2 out of 3 owners && 1 out of 2 super-owners , i.e. 3 out of 5 but at least one super-owner.

This would make distributing owner key control in bigger teams much simpler, which has nice security and backup properties, without sacrificing final control by key stakeholders like executive management.

• [ ] Allow for tx-crafter role that does not require a private key for signing ( UI & backend )

It would be useful to have a role as owner, if you will, that can only craft transactions to then be signed and executed by owners. Technically this ties into the previous point about different types of owners, since they key point is that the person who crafts tx should not be able to execute them. However, here I am thinking more of external company accountants that shouldnt have to deal with managing a private key but rather just have access on the Web UI to craft and submit tx to the queue and nothing more.

• [ ] Allow for multisending funds (Native & ERC20) via the premade interface

Very often we want to send funds to n number of people in one tx. So far the only way I could figure out to do this was using either Transaction Builder (very cumbersome) or CSV airdrop (great for mass payouts but not great for just smaller numbers like 3 or 4 transfers batched into one).

Therefore it would be great to have Multisend Funds option here that already deals with all the magic in the background.

Or even better include a + Add Transfer button here in the Send Funds modal:

Which allows you to specify n number of additional recipients , assets , and amounts

• [ ] Deep labelling / tagging of address book names

Sometimes when e.g. using CSV airdrop to make a mass payout with multiple ERC20 transfers the actual ERC20 transfer is nested deep in the call stack. On the Web UI and on mobile I noticed that, while it does recognize the multiple batched ERC20 transfers, it does not tag the destination address any more even if it's a labelled one from the address book. Obviously for security reasons it would be great to have enhanced support for human readable labelling also for deeply nested transfers

[rmeissner]

Hey @gitpusha thanks for the proposals and feature ideas.

Most of these require changes/ implementation effort in our web ui therefore I will move this issue to the safe-react repository.

Some of these features are already possible on a contract/ service level:

Different types of owners and policies: super-owners vs. owners

This can be accomplished by setting another Safe as a module for the Safe that is being governed. We have the strategy to support such setups (and other module flows) within the interface to make it possible cover more complex use cases.

Allow for tx-crafter role that does not require a private key for signing ( UI & backend )

Our backend already has a feature called delegates. These accounts are keys that have been whitelisted on the services to propose transactions and receive push notifications in the name of an owner. It might be an interesting idea to support them more naively in the web interface. For more information see our old devportal.

Thanks again and let us know if you have more ideas. In the future we will also additional channels to share your ideas. Stay tuned for news.

[katspaugh]

Thanks for the valuable feedback, @gitpusha. I'll close this now because:

• We now have Batch tx execution in the UI.
• Reg. tagging/labelling/airdrop management – we now have a Safe App called CSV Airdrop.
• Transaction drafting/delegation is its own epic we're tracking separately.