Event announcement: Aragon Permissions Workshop on May 5, 2020

Hello Aragonians!

I’m excited to share that on May 5th I will be hosting a virtual workshop along with Aragon One CTO Brett Sun (@sohkai). The workshop will be all about permissions in Aragon and you are all invited to join!

Like our other virtual events and meetings, this workshop will be livestreamed on the Aragon project YouTube channel. Anyone who wants to participate will be able to follow the stream live and ask questions in the YouTube Live Chat box or in the #support channel on Aragon Chat. You can also leave a question below if you can’t make it to the livestream and we’ll try to answer live on air.

During the first part of the workshop we’ll take a tour of the Permissions app. Then we’ll show how to use permissions to customize an Aragon organization. You are welcome to follow along on your own computer and replicate what we demonstrate. At the end we’ll leave time for Q&A in case you run into any problems, or have any other questions about Aragon permissions.

Here are the full details of the event for ease of reference:

What: Aragon Permissions Workshop hosted by John Light and Brett Sun
When: May 5, 2020 from 17:00-18:00 UTC
Where: https://youtu.be/kMF7Y_KPm-4
Event agenda:

  • Explore the Permissions app

  • Explain available permissions

  • Permissions tips, tricks, and “gotchas” to avoid

  • Demo: using permissions to evolve beyond the template

  • Audience Q&A

And here is a promo graphic by @owisixseven that you can share on social media to help us spread the word :smile:


Here’s the video link so you can watch a playback of the workshop:

Here are the organizations we were working off of during the demo:



Permissions diagram for the demo organizations:


And here are the links we mentioned throughout the workshop:

Aragon Permissions app documentation:

aragonOS Parameter Interpretation documentation:

Aragon Console documentation:

aragonCLI documentation:

PieDAO permissions structure:

Developer oriented permissions workshop this Friday May 8th:

1 Like

@light Will watch the playback! :smiley:


i also watched it now thanks to amazongirl

i have some questions:

What is the difference why don’t both assign to the the voting app? What does assign mean?

What is the difference between mint and issue tokens?

How does giving permission works? What kind of smart contract are needed for that?

Would be nice if I could see a big mouse to better follow the steps

Would be exiting to see a real possible use case Dao set up like starting a DAICO. I can better understand and connect it if I can relate to the real world use.

If I lock permission with the 0xburn address why is it locked? How does it work? You said I have to install a new finance app then. Will I loose all my funds? What is an app? a smart contract?

If I create a new minime token in the token app than it is a token with new token holders not a feature upgrade of the first one?

@Mouyou Would be happy to play around on testnet with you. :smiley: We could create a testnet DAICO and try out all the features! I think that’s really the best and most intuitive way to learn.

so we can make a tutorial while learning/playing with it. so just documenting the steps with screenshots. What are we going to do? like an example of a reddit community dao which want to raise money to create a community event and they can buy ticket (nft) with the community tokens.

I have no clue how to do this

In your screenshot, the Create new votes permission on the Voting app is assigned to the Tokens app so that anyone who holds a token issued by the Tokens app can create a vote. Whereas the Create new payments permission on the Finance app is assigned to the Voting app so that all payments have to be put to a vote before they can be executed.

This is explained in the Permissions section of the user guide:


  • Mint tokens: create new tokens and transfer them to a specified address
  • Issue tokens: create new tokens and transfer them to the organization’s Tokens app, for later assignment to a specified entity

For example, the “Add tokens” button in the Tokens app frontend uses the Mint tokens permission to create new tokens and transfer them to the specified address.

I recommend reading through the Permissions documentation for more info about that.

It’s locked because no one has the private key to the burn address, so no one can sign transactions needed to execute actions that require that permission. It is possible to lose all the funds in your organization if you lock certain permissions and aren’t able to execute the necessary transactions to get your money out. This is why I always recommend trying something on testnet before trying on mainnet, so you know the exact implications of what you’re doing with these smart contracts.

These questions are also answered in the user guide: https://help.aragon.org/article/6-anatomy-of-an-aragon-organization

Creating a new token does exactly what you think it does: it creates a new token. The old token stays the same, and a new token is created.