You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 21, 2019. It is now read-only.
The Permissions UI is not very intuitive when you want to grant permissions to token holders to be able to perform a specified action.
I understand wanting to be consistent with showing the application names, but as a new user to Aragon I would not have noticed such an amazing feature with the way it is worded now.
Maybe "Token Holders (FTL)" makes more sense...
The text was updated successfully, but these errors were encountered:
stellarmagnet
changed the title
Permissions - granting permission to token holders
Permissions - enhance terminology in relation to granting permission to token holders
Jan 20, 2019
I think "Token Holders" still makes the most sense. Here is another use case of where it will be displayed. I think "Tokens" being able to create new votes is not very intuitive
The thing is that Token Holders is not really the app, but what the app contains. Token Manager is correct but too verbose and technical, so that's why I think Tokens is a good balance
Wondering if we could provide more information about what the forwarding requirement is per app, as part of their published metadata.
That way, when selecting an app in that panel, or elsewhere, we could display this additional text so users would understand what requirements are imposed with an app owning a particular permission.
The Permissions UI is not very intuitive when you want to grant permissions to token holders to be able to perform a specified action.
I understand wanting to be consistent with showing the application names, but as a new user to Aragon I would not have noticed such an amazing feature with the way it is worded now.
Maybe "Token Holders (FTL)" makes more sense...
The text was updated successfully, but these errors were encountered: