Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Permissions app #6
The purpose of permissions app is to let users of a DAO view and manage permissions between users, apps and groups.
The permissions app allows many types of DAOs to be constructed via a visual interface.
Example 1: Allow Voting app (ie. token holder vote) to execute actions in another app - for instance minting new tokens in the Tokens app, or transferring tokens in the Finance app.
Example 2: Allow a token holder, or a group of token holders privileged access to certain app or apps.
-Nested permissions (a DAO having permissions in another DAO)
One example is that in this design you see "ASSIGN_ROLE" mapped to a human-readable "Assign tokens".
Where is the human readable definition of a Permission managed?
How does one update the human readable name of the Permission (I imagine people may think of better terminology over time to describe the role, that may not have been obvious at time of app deployment).
Do you mean of a Permission Manager?
As for how to describe those, it'd be here https://hack.aragon.org/docs/tutorial.html#writing-the-manifest-files
@jounih Pierre and I had a conversation today about getting data into the app and clarifying how everything works under the hood. The implementation's shaping up nicely!
I've added a few comments to the Invision based on notes from our conversation.
One of the major topics we touched upon was the creation of the first permission, since this is a special action that both requires more information, as well as access to a special role. We're thinking of designing a separate page in the app for this particular action, to give more information and help users understand the importance of who they choose to be the permission's "manager".