New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions app #6

Open
jounih opened this Issue Jul 22, 2018 · 4 comments

Comments

@jounih
Collaborator

jounih commented Jul 22, 2018

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.

TODO:

-Nested permissions (a DAO having permissions in another DAO)
-Constraints (for example, permission for only allowing transfer of < n tokens in n timeframe)

Clickthrough prototype:

https://invis.io/ENN3K3FR6Z4

Design:

webapp-1366px - permissions 2x

webapp-1366px - permissions app instance 2x

webapp-1366px - permissions add permission entity filled 2x

webapp-1366px - permissions app instance pending 2x

webapp-1366px - permissions modify permission 2x

webapp-1366px - permissions entity details 2x

@luisivan

This comment has been minimized.

Show comment
Hide comment
@luisivan

luisivan Jul 23, 2018

Member

Feedback:

  • Looks amazing
  • On Browse by entity in the main screen, Type should just be Entity, as we cannot determine if it's a User or any Contract. Also, I'd encourage to unify apps inside the Entity component, so an app would be displayed with its icon and its name, and maybe a tag specifying that it is an app. This way we have a component reusable everywhere, and we could also remove the Type column
Member

luisivan commented Jul 23, 2018

Feedback:

  • Looks amazing
  • On Browse by entity in the main screen, Type should just be Entity, as we cannot determine if it's a User or any Contract. Also, I'd encourage to unify apps inside the Entity component, so an app would be displayed with its icon and its name, and maybe a tag specifying that it is an app. This way we have a component reusable everywhere, and we could also remove the Type column
@stellarmagnet

This comment has been minimized.

Show comment
Hide comment
@stellarmagnet

stellarmagnet Jul 29, 2018

Question:

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).

stellarmagnet commented Jul 29, 2018

Question:

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).

@luisivan

This comment has been minimized.

Show comment
Hide comment
@luisivan

luisivan Jul 30, 2018

Member

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

Member

luisivan commented Jul 30, 2018

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

@sohkai

This comment has been minimized.

Show comment
Hide comment
@sohkai

sohkai Jul 31, 2018

Member

@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".

Member

sohkai commented Jul 31, 2018

@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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment